CVE-2025-12171: RESTful Content Syndication (WordPress plugin) · Unrestricted File Upload
Affects RESTful Content Syndication (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| anthonyeden RESTful Content Syndication | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-12171, organizations should take the following specific actions: 1) Immediately restrict access to the RESTful Content Syndication plugin settings to the minimum number of trusted administrators to reduce the risk of misuse. 2) Monitor and audit all file uploads through the plugin, especially those originating from the defined third-party server, to detect any anomalous or unauthorized files. 3) Implement web application firewall (WAF) rules to block or flag suspicious file upload attempts and potentially dangerous file types. 4) If possible, disable or remove the plugin until a vendor patch or update is released addressing the vulnerability. 5) Harden the third-party server used for ingestion by enforcing strict access controls, network segmentation, and continuous monitoring to prevent it from being used as an attack vector. 6) Employ file integrity monitoring on the WordPress server to detect unauthorized changes or uploads. 7) Educate administrators on the risks of this vulnerability and enforce strong authentication mechanisms, including multi-factor authentication, to reduce the risk of credential compromise. 8) Stay alert for official patches or updates from the vendor and apply them promptly once available. 9) Consider isolating the WordPress environment or running it with least privilege to limit the impact of potential exploitation.
Description
The RESTful Content Syndication plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the ingest_image() function in versions 1.1.0 to 1.5.0. This makes it possible for authenticated attackers, with Author-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible. This requires the attacker have access to a defined third-party server as specified in the settings, so it is unlikely that this will be exploitable by contributor-level users, and more likely to be exploited by administrators who also have access to the plugin's settings.