PHP code execution via unchecked function names
Published Feb 22, 2021 · Updated Aug 3, 2024
Code injection in Smarty before 3.1.39 allows template authors to execute arbitrary PHP through a malicious template function name. Smarty_Internal_Compile_Function accepted the name attribute without validating its characters, then incorporated the value into generated PHP code. Exploitation requires control of Smarty template source; injected PHP runs with the privileges of the process compiling or rendering the template.
Summary
What happened
Code injection in Smarty before 3.1.39 allows template authors to execute arbitrary PHP through a malicious template function name. Smarty_Internal_Compile_Function accepted the name attribute without validating its characters, then incorporated the value into generated PHP code. Exploitation requires control of Smarty template source; injected PHP runs with the privileges of the process compiling or rendering the template.
The record
- CVE
- CVE-2021-26120
- Published
- Feb 22, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-94, T1059
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Feb 22, 2021CVE 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
- Upstream illegal-function-name regression payloadproof 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