Uploading Svg\, Webp And Ico FilesWordPress extension · Uploading Svg\, Webp And Ico Files Project
CVE-2022-36285
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 · uneditedAuthenticated Arbitrary File Upload vulnerability in dmitrylitvinov Uploading SVG, WEBP and ICO files plugin <= 1.0.1 at WordPress.
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 confidenceAuthenticated users with access to the plugin's file upload functionality can upload arbitrary files, including potentially malicious SVG, WEBP, or ICO files. Since these file types can contain embedded scripts or be crafted to achieve remote code execution when served by the web server, an authenticated attacker could achieve RWE.
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
Uploading Svg\, Webp And Ico FilesWordPress extension
<= 1.0.1CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify if the plugin is installedIn the WordPress admin dashboard, go to Plugins > Installed Plugins and search for 'Uploading Svg, Webp And Ico Files' or check the wp-content/plugins directory for a folder containing these termsAffected if The plugin named 'Uploading Svg, Webp And Ico Files' appears in the installed plugins list
-
Check the installed versionIn WordPress admin, click on the plugin from the plugins list to view its details, or read the main plugin PHP file header for the Version fieldAffected if The version listed is 1.0.1 or lower
-
Verify the plugin is activeIn WordPress admin > Plugins, confirm the plugin shows as 'Active' rather than 'Inactive'Affected if The plugin is currently active and the version is 1.0.1 or lower
-
Confirm upload functionality is accessibleCheck if any non-admin user role (editor, author, contributor, subscriber) has access to media upload functionality provided by this specific plugin, or if the plugin exposes a public upload endpointAffected if Authenticated users with limited privileges can access the plugin's upload feature and the vulnerability is present in version 1.0.1 or lower
A user is affected if they have the 'Uploading Svg, Webp And Ico Files' plugin installed, active, at version 1.0.1 or lower, and have not restricted upload capabilities to trusted admin-only users.
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 dataUpdate the plugin to the latest version if a patch is available; otherwise, disable the plugin or restrict upload capabilities to only trusted admin users until remediation is possible.
Fix this in Uploading Svg\, Webp And Ico Files
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-2022-36285 — 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-2022-36285 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