Skip to content
Web

CVE-2026-15011

CRITICAL
Critical
EPSS 0.49%Patch availableJul 23, 2026

Unauthenticated code injection in Customer Support Ticket System & Helpdesk WP plugin via 'path' parameter.

common questions

Is CVE-2026-15011 being exploited?

Not confirmed. CVE-2026-15011 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.49% probability of exploitation in the next 30 days.

How severe is CVE-2026-15011?

CVE-2026-15011 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-15011?

Yes. A fix has been recorded for CVE-2026-15011. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-15011 affect?

CVE-2026-15011 affects Customer Support Ticket System & Helpdesk WordPress plugin <= 6.0.5, WordPress sites rendering [emd_form] shortcode. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-15011?

Update plugin to a patched release or deactivate/remove it; remove public [emd_form] shortcodes until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Customer Support Ticket System & Helpdesk WordPress plugin <= 6.0.5WordPress sites rendering [emd_form] shortcode
impact

Unauthenticated attackers can invoke arbitrary parameterless PHP functions, enabling data disclosure, site disruption, and potential site compromise.

action required

Immediate action required

affected versions
emarket-design Customer Support Ticket System & Helpdesk
  • affected<= 6.0.5

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free