Unauthenticated code execution via predictable template token
Published Jun 24, 2024 · Updated Aug 2, 2024
Code injection in PrestaShop M4 PDF Extensions before 3.3.2 allows remote attackers to execute arbitrary PHP via HTTP requests. M4PDF::saveTemplate() accepts attacker-controlled action_target and editor_content values through the public module front controller, relying only on a predictable token before writing executable PHP. No authentication or user interaction is required, and successful exploitation permits arbitrary code execution in the store's server context.
Summary
What happened
Code injection in PrestaShop M4 PDF Extensions before 3.3.2 allows remote attackers to execute arbitrary PHP via HTTP requests. M4PDF::saveTemplate() accepts attacker-controlled action_target and editor_content values through the public module front controller, relying only on a predictable token before writing executable PHP. No authentication or user interaction is required, and successful exploitation permits arbitrary code execution in the store's server context.
The record
- CVE
- CVE-2023-50029
- Published
- Jun 24, 2024
- Updated
- Aug 2, 2024
- Vendor
- PrestaShop
- Product
- M4 PDF Extensions
- Classifications
- CWE-94, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=3.3.1
What conditions does exploitation require?
What is affected?
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
- Friends of Presta HTTP proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- Web-skimmer deployment through M4 PDF Extensionsreported exploitation
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