CVE-2025-46507
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in ldrumm Unsafe Mimetypes unsafe-mimetypes allows Stored XSS.This issue affects Unsafe Mimetypes: from n/a through <= 0.1.4.
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 confidenceA CSRF vulnerability in the unsafe-mimetypes npm package (versions <= 0.1.4) by developer 'ldrumm' allows remote attackers to trick authenticated users into submitting requests that store malicious content, resulting in Stored XSS when other users encounter the crafted mimetype data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 if unsafe-mimetypes is installedInspect your project's package.json file under dependencies or devDependencies, or run 'npm list unsafe-mimetypes' in your project directoryAffected if The package is listed in dependencies or devDependencies
-
Verify the installed versionRun 'npm list unsafe-mimetypes' to see the exact version number, or check package-lock.json for the installed versionAffected if The installed version is 0.1.4 or lower (any version <= 0.1.4)
-
Identify usage of mimetype storage endpointsSearch your codebase for imports from 'unsafe-mimetypes' and identify where mimetype data from HTTP requests is being processed and stored (e.g., saved to a database, session, or file)Affected if Your application uses this package to process and store user-submitted mimetype data via HTTP requests
-
Check for CSRF protection on mimetype-handling routesReview your application's state-changing endpoints that handle mimetype input. Look for CSRF token validation middleware (such as csurf, express-csrf, or custom token verification)Affected if The endpoints that store mimetype data lack CSRF token validation or similar protection
-
Check if stored mimetypes are rendered without sanitizationSearch for code paths where stored mimetype data is rendered or output to users (e.g., in HTML, JSON responses, or template files) without sanitizationAffected if Stored mimetype data is displayed to users without output encoding or sanitization
You are affected if unsafe-mimetypes <= 0.1.4 is installed AND your application stores user-submitted mimetype data via HTTP requests AND those endpoints lack CSRF protection AND the stored data is rendered to other users without sanitization.
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.
dbcve · scopedImplement CSRF token validation on all state-changing endpoints and sanitize/validate mimetype inputs before storage; verify if a patched version exists or contact the maintainer.
Update to the latest version of Unsafe Mimetypes plugin (version > 0.1.4)
- 1. Identify all instances of the Unsafe Mimetypes plugin in your environment
- 2. Review the plugin for any unexpected file uploads or modified settings that may indicate exploitation
- 3. If the plugin is not actively used, consider removing it entirely to eliminate the attack surface
- 4. If the plugin is needed, check the WordPress plugin repository or vendor for a version newer than 0.1.4
- 5. Update the plugin to the latest available version which should contain the CSRF fix
- 6. After updating, verify the fix includes proper nonce validation for file upload operations
- 7. Clear any cached content if the plugin affects frontend output
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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 $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46507 — 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-46507 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