CVE-2025-45893
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenCart version 4.1.0.4 is vulnerable to a Stored Cross-Site Scripting (XSS) attack via SVG file uploads used in blog posts. The vulnerability arises because SVG files uploaded through the media manager are not properly sanitized. Attackers can craft a malicious SVG file containing embedded JavaScript
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceOpenCart 4.1.0.4 fails to sanitize SVG file uploads through its media manager when creating blog posts. Attackers can upload malicious SVG files containing embedded JavaScript that executes when other users view the blog post, leading to stored XSS.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 4.1.0.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed OpenCart versionAccess the admin dashboard and navigate to System > Settings, or check the version.php file in the system/library folder. Compare the version number to the affected range: <= 4.1.0.4Affected if The installed version is 4.1.0.4 or lower
-
Verify media manager is accessibleLog in to the admin panel and confirm you can access the Media Manager (typically under Content > Media or a similar path). This feature must be available for the vulnerability to apply.Affected if The media manager module is enabled and accessible to user accounts who can create blog posts
-
Confirm SVG upload capability existsAttempt to upload a test file through the media manager. Check if .svg files are accepted in the allowed file type configuration, or inspect the system/library/mimes.php or equivalent upload configuration for SVG MIME types.Affected if SVG file extensions are included in the allowed upload types for the media manager
-
Check blog post creation featureNavigate to the blog post creation interface in the admin panel (typically under Catalog > Blogs or Content > Blogs). Confirm that the media manager can be invoked while creating or editing a blog post.Affected if Blog posts can be created or edited and the media manager is usable within that context
-
Inspect uploaded SVG files in systemSearch the storage or media directory for .svg files that may have been uploaded. Common paths include storage/ or image/catalog/ directories. Examine any found SVG files for embedded script tags, event handlers (onload, onclick, etc.), or foreignObject elements.Affected if SVG files exist in the system that contain executable JavaScript, script tags, or event handler attributes
A user is affected if they run OpenCart version 4.1.0.4 or lower with the media manager enabled and SVG file uploads permitted, particularly if blog posts can display user-uploaded SVG content.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict SVG sanitization on upload to strip or disable script elements, event handlers, and foreignObject references; alternatively, block SVG uploads entirely or restrict to trusted users only.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-45893 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-45893 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data