Arbitrary code execution via stored XSS cache poisoning
Published Jun 15, 2023 · Updated Mar 5, 2025
Stored XSS in Adobe Commerce 2.4.6 and earlier allows remote authenticated users with admin privileges to execute arbitrary code. The CNA identifies cache poisoning, while Adobe classifies the flaw as stored XSS but does not disclose the affected code path or unsafe template operation. Administrative credentials are required; exploitation needs no user interaction and grants code execution in the server context.
Summary
What happened
Stored XSS in Adobe Commerce 2.4.6 and earlier allows remote authenticated users with admin privileges to execute arbitrary code. The CNA identifies cache poisoning, while Adobe classifies the flaw as stored XSS but does not disclose the affected code path or unsafe template operation. Administrative credentials are required; exploitation needs no user interaction and grants code execution in the server context.
The record
- CVE
- CVE-2023-29297
- Published
- Jun 15, 2023
- Updated
- Mar 5, 2025
- Vendor
- Adobe
- Product
- Adobe Commerce
- Classifications
- CWE-79, CWE-1336, T1190
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jun 15, 2023CVE publishedPublication date reported by the CVE source.
- Mar 5, 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=unspecified <=2.4.4-p3
- Affected versionversion=unspecified <=2.4.5-p2
- Affected versionversion=unspecified <=2.4.6
- Affected versionversion=unspecified <=None
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
No public exploit references are available in this record.
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