Vulnerability in Single Sign On For TNG (WordPress plugin) (CVE-2026-15964)
Summary
Vulnerability in Single Sign On For TNG (WordPress plugin) (CVE-2026-15964). Successful exploitation can lead to full system takeover. Exploitable via wp_ajax_nopriv_ssoprocess_ajax.
Original description
The description as published by the source.
The Single Sign On For TNG plugin for WordPress is vulnerable to Authentication Bypass via unauthenticated password reset in all versions up to, and including, 2.0.0. This is due to the ssoprocess_ajax() function — registered on wp_ajax_nopriv_ssoprocess_ajax and therefore reachable without authentication — accepting an attacker-supplied email parameter with the setnewpassword operation and calling reset_password() on the resolved account without any ownership token, email confirmation link, or capability check. The sole guard is a call to check_ajax_referer(), which provides no authorization barrier because the ssoajaxnonce nonce is publicly broadcast on every front-end page via wp_localize_script() into the SSOPWDREQUIREMENT JavaScript object; since WordPress computes nonces for logged-out visitors against a shared anonymous session context, any unauthenticated visitor can scrape a valid nonce from the homepage and use it to authenticate the request. This makes it possible for unauthenticated attackers to change the password of any WordPress account, including administrator accounts, enabling complete site takeover.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-15964 has been found in Single Sign On For TNG (WordPress plugin).
Attackers can target a specific entry point like wp_ajax_nopriv_ssoprocess_ajax over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Single Sign On For TNG (WordPress plugin) CVE-2026-15964" on the vendor's site.
CVE-2026-15964 (Single Sign On For TNG (WordPress plugin)) — CWE-620 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: wp_ajax_nopriv_ssoprocess_ajax / email / setnewpassword / ssoajaxnonce
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-620) exists in Single Sign On For TNG (WordPress plugin). Attackers reach the vulnerable code path via wp_ajax_nopriv_ssoprocess_ajax without authentication.
Check the vendor advisory for the affected versions of Single Sign On For TNG (WordPress plugin). Attack surface: wp_ajax_nopriv_ssoprocess_ajax / email / setnewpassword / ssoajaxnonce.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Single Sign On For TNG (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web nvd.nist.gov
- web github.com