CVE-2025-45892: OpenCart · Cross-site Scripting
Source CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate CVE-2025-45892, organizations should immediately upgrade OpenCart to a patched version once available from the vendor. In the absence of an official patch, administrators should implement strict input validation and output encoding on the blog editor inputs to neutralize malicious scripts. Employing a Web Application Firewall (WAF) with rules to detect and block XSS payloads targeting the blog editor can provide interim protection. Regularly audit and sanitize existing blog content to remove any injected scripts. Enforce the Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. Additionally, limit blog editor access to trusted users and implement multi-factor authentication to reduce the risk of unauthorized content submission. Monitoring web logs for unusual activity related to blog content submissions can help detect exploitation attempts early. Finally, educate content editors and administrators about secure content handling practices and the risks of XSS attacks.
Description
OpenCart version 4.1.0.4 is vulnerable to a Stored Cross-Site Scripting (XSS) attack via the blog editor. The vulnerability arises because input in the blog's editor is not properly sanitized or escaped before being rendered. This allows attackers to inject malicious JavaScript code