Stored XSS via unsanitized blog editor input
Published Jul 25, 2025 · Updated Jul 25, 2025
Stored XSS in the OpenCart 4.1.0.4 blog editor allows remote attackers to execute JavaScript in a visitor's browser. The editor stores blog content without adequately sanitizing or escaping attacker-controlled input before the content is rendered. Exploitation requires a visitor to view the malicious blog post, exposing browser-accessible data and actions in that visitor's session.
Summary
What happened
Stored XSS in the OpenCart 4.1.0.4 blog editor allows remote attackers to execute JavaScript in a visitor's browser. The editor stores blog content without adequately sanitizing or escaping attacker-controlled input before the content is rendered. Exploitation requires a visitor to view the malicious blog post, exposing browser-accessible data and actions in that visitor's session.
The record
- CVE
- CVE-2025-45892
- Published
- Jul 25, 2025
- Updated
- Jul 25, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 25, 2025CVE publishedPublication date reported by the CVE source.
- Jul 25, 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
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