ContentStudio <= 1.3.7 - Authenticated (Author+) Arbitrary File Upload
Strategic Overview
- Status
- Patched in 1.4.0
- Affected Plugin
- ContentStudio
- Affected Version
<= 1.3.7- CVSS
- 8.8High
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2025-12181
At a glance
CVE-2025-12181 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the ContentStudio WordPress plugin, affecting versions <= 1.3.7. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 1.4.0; sites on affected versions should update now. Disclosed December 2025, reported by kr0d.
Vulnerability Overview
The ContentStudio plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the cstu_update_post() function in all versions up to, and including, 1.3.7. 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. CVE-2025-67910 is likely a duplicate of this.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-434: Unrestricted Upload of File with Dangerous Type
ContentStudio <= 1.3.7 carries this weakness at cstu_update_post(), and reaching it takes an account at Author level or above. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.
If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For ContentStudio the fix is 1.4.0: builds <= 1.3.7 are affected, anything from 1.4.0 onward is not.
Remediation
Update to version 1.4.0, or a newer patched version
How does WordSec protect against this?
An attacker needs Author access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: ContentStudio 1.4.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in ContentStudio
- 9.8CVE-2023-0556: ContentStudio <= 1.2.5 Missing Authorization
CVE-2023-0556 - 9.8ContentStudio <= 1.1.8 Missing Authorization
- 8.2CVE-2023-0558: ContentStudio <= 1.2.5 Authorization Bypass
CVE-2023-0558 - 7.5CVE-2023-0557: ContentStudio <= 1.2.5 Information Exposure
CVE-2023-0557 - 5.3CVE-2025-49990: ContentStudio <= 1.3.7 Missing Authorization
CVE-2025-49990 - 4.3CVE-2025-13144: ContentStudio <= 1.3.7 CSRF to Settings Update
CVE-2025-13144 - 4.3CVE-2025-47692: ContentStudio <= 1.3.5 Missing Authorization
CVE-2025-47692
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C