Arbitrary code execution via include-expression code splicing
Published Mar 15, 2023 · Updated Feb 27, 2025
Code injection in swig-templates 2.0.4 and earlier and swig 1.4.2 and earlier allows attackers to execute code through crafted templates. The include tag compiler splices its file expression into generated JavaScript that the parser appends to output used to construct and invoke an anonymous function. Rendering an attacker-controlled template is required, and successful exploitation runs commands with the Node.js process's privileges.
Summary
What happened
Code injection in swig-templates 2.0.4 and earlier and swig 1.4.2 and earlier allows attackers to execute code through crafted templates. The include tag compiler splices its file expression into generated JavaScript that the parser appends to output used to construct and invoke an anonymous function. Rendering an attacker-controlled template is required, and successful exploitation runs commands with the Node.js process's privileges.
The record
- CVE
- CVE-2023-25344
- Published
- Mar 15, 2023
- Updated
- Feb 27, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-94, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 15, 2023CVE publishedPublication date reported by the CVE source.
- Feb 27, 2025Record 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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 include-tag code-execution 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