Authenticated code execution via unsanitized include path
Published Jun 6, 2024 · Updated Feb 13, 2025
Path traversal in CubeCart 6.5.5 and earlier allows remote authenticated users to execute PHP code through crafted _g parameters. The admin routing logic appends .inc.php to the _g-derived path and passes it to include() without removing traversal sequences. Any admin-panel account suffices, but exploitation also requires an attacker-controlled .inc.php file already present anywhere the server process can read.
Summary
What happened
Path traversal in CubeCart 6.5.5 and earlier allows remote authenticated users to execute PHP code through crafted _g parameters. The admin routing logic appends .inc.php to the _g-derived path and passes it to include() without removing traversal sequences. Any admin-panel account suffices, but exploitation also requires an attacker-controlled .inc.php file already present anywhere the server process can read.
The record
- CVE
- CVE-2024-34832
- Published
- Jun 6, 2024
- Updated
- Feb 13, 2025
- Vendor
- CubeCart Limited
- Product
- CubeCart
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 6, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=6.5.5
What conditions does exploitation require?
What is affected?
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
- CubeCart Directory Traversal May Lead To RCEproof 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