Skip to content
feed: live
0dayNews
CVE Record
[ CRITICAL ]CVE-2026-15341

User Session Synchronizer: Unauthenticated Account Takeover

User Session Synchronizer WP plugin (≤1.4.0) has no auth check on its session-sync handler, letting unauthenticated attackers hijack any WordPress account.

Vendor
User Session Synchronizer
Product
User Session Synchronizer for WordPress
CVSS
9.8
EPSS (exploit probability)
0.6%
Status
patched
Published

Is CVE-2026-15341 being exploited?

Not on any exploited-vulnerability catalog we track. CVE-2026-15341 was not on the CISA, ENISA or CIRCL exploited catalogs as of our 2026-11-22 snapshot. That can change quickly; check the write-up below for the latest reporting.

FIRST's EPSS model puts the probability of exploitation activity in the next 30 days at 0.6% (scored October 14, 2026).

Catalog snapshot 2026-11-22. Full cross-catalog view: /kev-comparison

CVE-2026-15341 timeline

  1. First 0dayNews coveragesame day as NVD
  2. Published to NVD

Every event links to its source. Catalog dates are each catalog's own; day offsets count from NVD publication. Data: JSON

The User Session Synchronizer plugin for WordPress (all versions through 1.4.0) runs a synchronize_session() function hooked on the WordPress init action, meaning it fires on every request to the site. The function accepts three POST parameters — ussync-key, ussync-token, and ussync-ref — with no nonce check, no capability check, and no shared-secret validation. When ussync-key references an unregistered slot, get_option() returns false, triggering a fallback code path that still resolves the referenced WordPress user and issues them an authenticated session.

The practical impact: any unauthenticated visitor can obtain a valid session for any WordPress account on the site, including site administrators, by supplying a known or guessed user identifier. No prior authentication is required.

Affected versions: all versions through 1.4.0
Fixed in: 1.4.1
What to do: Update the plugin immediately via the WordPress admin plugin manager. There is no safe configuration workaround for affected versions.

See also: full write-up covering this and two related critical WordPress plugin flaws.