Unauthenticated PHP code execution via attachment parameter
Published Jan 14, 2020 · Updated Aug 6, 2024
Code execution in Jcow CMS 4.x through 4.2 and 5.x through 5.2 allows remote attackers to run arbitrary PHP via attachment. In includes/libs/ss.inc.php, the handler uses the unsanitized POST attachment value to construct a module include path and an eval-built ajax_post call. No authentication or user interaction is required, and successful exploitation runs attacker-selected PHP code in the web server context.
Summary
What happened
Code execution in Jcow CMS 4.x through 4.2 and 5.x through 5.2 allows remote attackers to run arbitrary PHP via attachment. In includes/libs/ss.inc.php, the handler uses the unsanitized POST attachment value to construct a module include path and an eval-built ajax_post call. No authentication or user interaction is required, and successful exploitation runs attacker-selected PHP code in the web server context.
The record
- CVE
- CVE-2011-3203
- Published
- Jan 14, 2020
- Updated
- Aug 6, 2024
- Vendor
- Jcow
- Product
- Jcow CMS
- Classifications
- CWE-20, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record 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=4.x to 4.2 and 5.x to 5.2
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.
Public exploit references
- Metasploit jcow_eval moduleproof of concept · unverified
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