Unauthenticated code execution via unfiltered encryption key
Published Mar 24, 2022 · Updated Aug 3, 2024
Code injection in Ionize CMS 1.0.8.1 allows remote attackers to execute arbitrary PHP code through the web-based installer. Installer.php writes the unfiltered Encryption Key field directly into application/config/config.php, where injected PHP syntax becomes executable configuration. The installation interface must remain reachable; exploitation needs no authentication and grants code execution in the web server context.
Summary
What happened
Code injection in Ionize CMS 1.0.8.1 allows remote attackers to execute arbitrary PHP code through the web-based installer. Installer.php writes the unfiltered Encryption Key field directly into application/config/config.php, where injected PHP syntax becomes executable configuration. The installation interface must remain reachable; exploitation needs no authentication and grants code execution in the web server context.
The record
- CVE
- CVE-2022-26272
- Published
- Mar 24, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 24, 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
- Ionize issue 403 proof of conceptproof of concept · 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