Enable Svg\, Webp \& Ico UploadWordPress extension · Ideastocode
CVE-2023-2143
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 · uneditedThe Enable SVG, WebP & ICO Upload WordPress plugin through 1.0.3 does not sanitize SVG file contents, leading to a Cross-Site Scripting vulnerability.
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 · high confidenceThe Enable SVG, WebP & ICO Upload WordPress plugin through version 1.0.3 accepts SVG file uploads without sanitizing their contents. Since SVG files can contain embedded JavaScript, an attacker can upload a malicious SVG that executes arbitrary script in the browser of any user who views or accesses the file, 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
Enable Svg\, Webp \& Ico UploadWordPress extension
<= 1.0.3CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Verify the plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Enable SVG, WebP & ICO Upload' by Ideastocode. Check if it is installed and active.Affected if The plugin is present and activated in WordPress
-
Check the plugin versionIn the plugins list, click on the plugin to view details, or inspect the plugin header in /wp-content/plugins/enable-svg-webp-ico-upload/ directory to confirm the version number.Affected if The version is 1.0.3 or lower
-
Confirm SVG upload functionality is availableAttempt to upload an SVG file through the WordPress Media Library uploader (or check plugin settings if a settings page exists) to verify the upload capability is functioning.Affected if SVG files can be uploaded through the media uploader
-
Identify SVG files in the media libraryIn WordPress admin, go to Media > Library and filter or search for .svg files. Check the uploads directory /wp-content/uploads/ for SVG files.Affected if SVG files have been uploaded to the site
If the plugin version is 1.0.3 or lower and SVG uploads are permitted, the environment is affected by this stored XSS vulnerability.
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 server-side sanitization of SVG file contents using a dedicated library (e.g., DOMPurify) to strip script tags and event handlers before allowing uploads, and restrict SVG upload permissions to trusted users only.
Fix this in Enable Svg\, Webp \& Ico Upload
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2143 — 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-2023-2143 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