cve.bz

CVE-2026-123097 WP Remote Users Sync < 2.2.1 - Privilege Escalation to Administrator via 'create' and 'update' Sync Actions

7.5 highEPSS 0.2%

High (7.5) in unknown wp remote users sync. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
The WP Remote Users Sync WordPress plugin before 2.2.1 does not restrict which account fields a synchronised site may set when it creates or updates users, allowing a site holding the shared synchronisation keys to assign the administrator role, modify any existing account and write arbitrary user metadata, bypassing the receiving site's role and metadata restrictions.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 6th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-269 Improper Privilege Management
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
Assigned by
WPScan (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-123097 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123097?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123097?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-123097 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-123097

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-123097](https://cve.bz/cve/badge/CVE-2026-123097.svg)](https://cve.bz/cve/CVE-2026-123097)

HTML:

<a href="https://cve.bz/cve/CVE-2026-123097"><img src="https://cve.bz/cve/badge/CVE-2026-123097.svg" alt="CVE-2026-123097"></a>

Affected

  • unknown:wp remote users sync

Attack patterns (CAPEC)

  • CAPEC-58 Restful Privilege Elevation Likelihood: High · Severity: High
  • CAPEC-122 Privilege Abuse Likelihood: High · Severity: Medium
  • CAPEC-233 Privilege Escalation

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis
  2. Scored 7.5 high

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON