Unauthenticated code execution via arbitrary file write
Published May 22, 2023 · Updated Jan 28, 2025
Arbitrary file write in Wcms 0.3.2 allows remote attackers to execute commands through crafted requests to /wcms/wex/html.php. The handler passes the GET finish value directly as the destination path and POST textAreaCode data as contents to file_put_contents(). No authentication or user interaction is required, and PHP code written into the web directory executes with the web server's privileges when requested.
Summary
What happened
Arbitrary file write in Wcms 0.3.2 allows remote attackers to execute commands through crafted requests to /wcms/wex/html.php. The handler passes the GET finish value directly as the destination path and POST textAreaCode data as contents to file_put_contents(). No authentication or user interaction is required, and PHP code written into the web directory executes with the web server's privileges when requested.
The record
- CVE
- CVE-2023-31689
- Published
- May 22, 2023
- Updated
- Jan 28, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-434, T1505.003, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 22, 2023CVE publishedPublication date reported by the CVE source.
- Jan 28, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Wcms html.php arbitrary file-write proof of conceptfunctional · demonstrated
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