Authenticated PHP code execution via cache-file injection
Published Sep 28, 2021 · Updated Aug 4, 2024
Static code injection in Wuzhi CMS 4.1.0 allows remote authenticated users to execute PHP code through attachment settings. The attachment administration set() method passes the unfiltered setting value to set_cache(), which writes non-array input verbatim into an executable PHP cache file that get_cache() loads on the next request. A valid back-end session and access to the attachment settings action are required; successful exploitation executes attacker-supplied PHP with the web application process privileges.
Summary
What happened
Static code injection in Wuzhi CMS 4.1.0 allows remote authenticated users to execute PHP code through attachment settings. The attachment administration set() method passes the unfiltered setting value to set_cache(), which writes non-array input verbatim into an executable PHP cache file that get_cache() loads on the next request. A valid back-end session and access to the attachment settings action are required; successful exploitation executes attacker-supplied PHP with the web application process privileges.
The record
- CVE
- CVE-2020-20124
- Published
- Sep 28, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-96, CWE-94, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 28, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
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
- Upstream issue proof of conceptproof 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