# CVE-2026-123092: WP Remote Users Sync < 2.3.0 - Privilege Escalation to Administrator via 'meta' Sync Action

Status: published. Published: 2026-11-12. Updated: 2026-11-12.

The WP Remote Users Sync WordPress plugin before 2.3.0 does not restrict which user metadata keys may be written through its incoming user synchronisation requests, allowing a site that holds the shared synchronisation keys to set the capabilities of any existing account and escalate it to administrator.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Unknown / WP Remote Users Sync: ≥ 0; < 2.3.0 (affected, semver). Source: CNA: WPScan

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-269

## Exploit evidence

- exploit: https://wpscan.com/vulnerability/31ed11db-eb07-4628-8ad8-5b545c6f8fe0/ (CNA: WPScan)

## References

- https://wpscan.com/vulnerability/31ed11db-eb07-4628-8ad8-5b545c6f8fe0/ (CNA: WPScan; exploit, vdb-entry, technical-description)

## Provenance

- CNA: WPScan: https://www.cve.org/CVERecord?id=CVE-2026-123092; retrieved 2026-11-12; source updated 2026-11-12

Revision: 78219add41b89072efc5f155e2ec83c4493494651730ccc21e244a84769417b0

Canonical: https://y2.dev/cve/CVE-2026-123092

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.