Skip to content
Web

CVE-2026-73350

HIGH
High
EPSS 0.40%Aug 19, 2026

Unauthenticated authentication bypass in SupportCandy <=3.5.1 plugin.

common questions

Is CVE-2026-73350 being exploited?

Not confirmed. CVE-2026-73350 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.40% probability of exploitation in the next 30 days.

How severe is CVE-2026-73350?

CVE-2026-73350 is rated High. 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-73350?

Not known from our data. No patch reference has been recorded for CVE-2026-73350, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-73350 affect?

CVE-2026-73350 affects SupportCandy <= 3.5.1, WordPress sites using SupportCandy plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-73350?

Disable or remove SupportCandy until vendor patch; block plugin access and monitor logs.

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

executive summary
technical analysis
affected
SupportCandy <= 3.5.1WordPress sites using SupportCandy plugin
impact

Unauthenticated attackers can bypass login to view/modify support tickets and perform actions as users or admins, enabling data exposure and account takeover.

action required

Immediate action required

affected versions
PSM Plugins SupportCandy
  • affected<= 3.5.1

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