Code execution via crafted PHP template file
Published Feb 23, 2022 · Updated Aug 3, 2024
Arbitrary code execution in WBCE CMS 1.5.2 allows attackers to run PHP code through a crafted file handled by templates/install.php. Public records identify only the crafted PHP file and the templates/install.php handler; the validation or file-handling failure is undisclosed. NVD scores the attack as local with required user interaction, and successful exploitation runs arbitrary PHP code in the CMS context.
Summary
What happened
Arbitrary code execution in WBCE CMS 1.5.2 allows attackers to run PHP code through a crafted file handled by templates/install.php. Public records identify only the crafted PHP file and the templates/install.php handler; the validation or file-handling failure is undisclosed. NVD scores the attack as local with required user interaction, and successful exploitation runs arbitrary PHP code in the CMS context.
The record
- CVE
- CVE-2022-25101
- Published
- Feb 23, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1204.002
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Feb 23, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
No public exploit references are available in this record.
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