Unauthenticated code execution via installer configuration write
Published Mar 31, 2022 · Updated Aug 4, 2024
Remote code execution in The-Secretary 2.5 allows remote attackers to execute PHP code through the web-based installer. The install.php script writes an unsanitized database name into system/assistants/config.inc.php, and requesting that generated file executes injected PHP. Exploitation requires a reachable install.php endpoint; successful code runs with the web server account's permissions.
Summary
What happened
Remote code execution in The-Secretary 2.5 allows remote attackers to execute PHP code through the web-based installer. The install.php script writes an unsanitized database name into system/assistants/config.inc.php, and requesting that generated file executes injected PHP. Exploitation requires a reachable install.php endpoint; successful code runs with the web server account's permissions.
The record
- CVE
- CVE-2021-43479
- Published
- Mar 31, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 31, 2022CVE 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
- install.php database-name PHP injection 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