Skip to content
Web

CVE-2026-15964

9.8
Critical
EPSS 0.63%Aug 1, 2026

Unauthenticated password-reset bypass in Single Sign On For TNG WordPress plugin.

common questions

Is CVE-2026-15964 being exploited?

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

How severe is CVE-2026-15964?

CVE-2026-15964 is rated Critical with a CVSS score of 9.8. 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-15964?

Not known from our data. No patch reference has been recorded for CVE-2026-15964, 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-15964 affect?

CVE-2026-15964 affects Single Sign On For TNG WordPress plugin ≤ 2.0.0, WordPress sites using that plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-15964?

Remove/disable plugin; block its AJAX endpoint; enforce 2FA and rotate admin credentials; apply vendor patch when available.

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

executive summary
technical analysis
affected
Single Sign On For TNG WordPress plugin ≤ 2.0.0WordPress sites using that plugin
impact

Unauthenticated attackers can reset any account password, including admins, enabling full WordPress site takeover.

action required

Immediate action required

affected versions
britcoder Single Sign On For TNG
  • affected<= 2.0.0

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