CVE-2026-123092 · Package
NO FIX YET · SEE WHAT TO DO
The WP Remote Users Sync WordPress plugin before 2.3.0 does not restrict which user metadata keys incoming synchronisation requests may write. A site holding the shared synchronisation keys can set the capabilities of any existing account and raise it to administrator.
first public Nov 12, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Sites running the WP Remote Users Sync plugin before 2.3.0 that accept user synchronisation requests from remote sites. The exposure depends on a party holding the shared synchronisation keys, so sites without remote user sync configured are likely not reachable this way. unknown whether any sources detail further conditions.
Not affected if plugin-2.3.0-or-later, remote-sync-disabled
Who cares self-hosted, wordpress, wp-remote-users-sync
2.3.0 as affected.2.3.0 or later.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.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.