Session takeover via stored form-field scripts
Published Aug 12, 2025 · Updated Feb 26, 2026
Stored XSS in affected Adobe Commerce releases allows remote authenticated users to take over a victim application session. A low-privileged user can store a malicious script in a vulnerable form field, but Adobe has not identified the field or disclosed the code path that fails to neutralize its contents. Execution requires a victim to visit the affected page, where the script runs in the victim context and can compromise session confidentiality and integrity.
Summary
What happened
Stored XSS in affected Adobe Commerce releases allows remote authenticated users to take over a victim application session. A low-privileged user can store a malicious script in a vulnerable form field, but Adobe has not identified the field or disclosed the code path that fails to neutralize its contents. Execution requires a victim to visit the affected page, where the script runs in the victim context and can compromise session confidentiality and integrity.
The record
- CVE
- CVE-2025-49557
- Published
- Aug 12, 2025
- Updated
- Feb 26, 2026
- Vendor
- Adobe
- Product
- Adobe Commerce
- Classifications
- CWE-79
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 12, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record 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 <=2.4.4-p14
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
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