User Session Synchronizer <= 1.4.0 — Unauthenticated Authentication Bypass to Account Takeover via 'ussync-key', 'ussync-token', and 'ussync-ref' Parameters
CVE-2026-15341Published · Updated Action summary
Affected: ≤1.4.0No patch available
What to do until a fix ships- Severity
- Critical9.8
- CVSS
- 9.8CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:NPrivileges required- None
UI:NUser interaction- None
S:UScope- Unchanged
C:HConfidentiality- High
I:HIntegrity- High
A:HAvailability- High
- Weakness
- CWE-287 Improper Authentication
- Required access
- No account needed
- Exploit prediction (EPSS)
- No score
- CISA KEV
- Not listed
On this page8
Am I affected?
User Session Synchronizer user-session-synchronizer
- Affected≤ 1.4.0
- PatchedNo fix yet
No patched version available.
You are affected if you run ≤ 1.4.0. No fixed version has been released.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under User Session Synchronizer.
- No admin access? Run a passive check of your site. It reads public files only.
- No account is needed to exploit this. Treat any exposed site on an affected version as at risk.
What to do
- No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch User Session Synchronizer to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to Afan, moonge.
The User Session Synchronizer plugin for WordPress is vulnerable to Authentication Bypass leading to Account Takeover in all versions up to, and including, 1.4.0. The `synchronize_session()` function, hooked on `init` and therefore executed on every request, performs no nonce, capability, or shared-secret validation against the attacker-supplied `ussync-key`, `ussync-token`, and `ussync-ref` parameters; when `ussync-key` references an unregistered slot, `get_option()` returns `false` for both the secret key and the domain list, causing the AES-256-CBC encryption key to degrade to the fully predictable `md5('')` and the referer allowlist to collapse to an empty-string match, while the AES IV is unconditionally hard-coded as `md5('another-secret')`. This makes it possible for unauthenticated attackers to supply a crafted request encrypting any known or guessable user email address in the `ussync-ref` parameter, causing the handler to call `wp_set_auth_cookie()` for the matched user and granting full authentication as that user — including administrators — with no prior knowledge of site secrets.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
More in User Session Synchronizer
All 2| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.1 | Cross-Site Request Forgery to Stored Cross-Site Scripting ≤1.4.0No patch available | CVE-2025-32612 |
- Medium6.1Cross-Site Request Forgery to Stored Cross-Site Scripting
≤1.4.0No patch available
Timeline
CVE published
Severity critical, CVSS 9.8
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- [object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.
