Contributor file upload via remote image fetch
Published Aug 18, 2026 · Updated Aug 18, 2026
Arbitrary file upload in Sync Post With Other Site through 1.9.3 allows remote authenticated users to write files via crafted sync requests. In includes/sps_sync.class.php, the public /sps/v1/data REST route accepts any caller, and sps_get_request authorizes any account with edit_posts before sps_add_update_post and spsp_grab_content_images fetch attacker-supplied featured_image and img src URLs with wp_remote_request and write the response body into wp_upload_dir() with fopen before type checks. A Contributor account is sufficient because that WordPress role has edit_posts; if the uploads path executes PHP, the write primitive yields code execution, otherwise it still places attacker-chosen files in web-accessible storage.
Summary
What happened
Arbitrary file upload in Sync Post With Other Site through 1.9.3 allows remote authenticated users to write files via crafted sync requests. In includes/sps_sync.class.php, the public /sps/v1/data REST route accepts any caller, and sps_get_request authorizes any account with edit_posts before sps_add_update_post and spsp_grab_content_images fetch attacker-supplied featured_image and img src URLs with wp_remote_request and write the response body into wp_upload_dir() with fopen before type checks. A Contributor account is sufficient because that WordPress role has edit_posts; if the uploads path executes PHP, the write primitive yields code execution, otherwise it still places attacker-chosen files in web-accessible storage.
The record
- CVE
- CVE-2026-32463
- Published
- Aug 18, 2026
- Updated
- Aug 18, 2026
- Vendor
- Kamlesh Parmar
- Product
- Sync Post With Other Site
- Classifications
- CWE-434, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 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=n/a <=1.9.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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