Authenticated internal-service access via unrestricted ping destination
Published Aug 16, 2023 · Updated Apr 8, 2026
Server-side request forgery in WP Remote Users Sync 1.2.12 and earlier allows remote authenticated users to access internal services. The notify_ping_remote AJAX handler accepts an attacker-controlled destination and directs the WordPress server to request it without restricting the target. Subscriber-level access is sufficient to query or modify information exposed by internal services that trust requests from the WordPress host.
Summary
What happened
Server-side request forgery in WP Remote Users Sync 1.2.12 and earlier allows remote authenticated users to access internal services. The notify_ping_remote AJAX handler accepts an attacker-controlled destination and directs the WordPress server to request it without restricting the target. Subscriber-level access is sufficient to query or modify information exposed by internal services that trust requests from the WordPress host.
The record
- CVE
- CVE-2023-3958
- Published
- Aug 16, 2023
- Updated
- Apr 8, 2026
- Vendor
- Alexandre Froger
- Product
- WP Remote Users Sync
- Classifications
- CWE-918, CAPEC-664, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 16, 2023CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.2.12
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo