Pro Mime TypesWordPress extension · Cyberwire
CVE-2023-32502
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 Sybre Waaijer Pro Mime Types – Manage file media types plugin <= 1.0.7 versions.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Pro Mime Types WordPress plugin allows attackers to trick authenticated users into performing unintended actions (likely modifying media type configurations) by forcing their browser to send malicious requests to the affected site.
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
Pro Mime TypesWordPress extension
< 2.0.0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Locate the Pro Mime Types plugin installationCheck your WordPress plugins directory at wp-content/plugins/ for a folder named 'pro-mime-types' or similar variant containing 'mime-types' in the name.Affected if The plugin folder is present in the plugins directory.
-
Identify the installed plugin versionOpen the main PHP file of the plugin and locate the plugin header comment which contains the 'Version:' field, or check any version.php file if present in the plugin folder.Affected if The version number found is less than 2.0.0.
-
Verify presence of admin configuration formsInspect the plugin PHP files for form handlers that process media type or MIME type configuration submissions, typically found in files handling settings, admin menus, or AJAX endpoints.Affected if Form processing code exists that handles mime type configuration without visible nonce token validation.
-
Confirm WordPress user authentication is requiredReview the affected code paths to verify they require administrator or editor privileges to access the mime type configuration settings.Affected if The plugin requires logged-in WordPress users to modify mime type settings, meaning attackers could target authenticated administrators.
If the Cyberwire Pro Mime Types plugin is installed with a version lower than 2.0.0 and contains admin forms for configuring mime types, the site is vulnerable to CSRF attacks via forced browser requests from authenticated administrators.
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 · scoped2.0.0
Implement anti-CSRF tokens (nonces) on all form submissions and AJAX requests in the plugin, and validate Origin/Referer headers server-side to ensure requests originate from legitimate sources.
Pro Mime Types version 2.0.0 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the Pro Mime Types plugin
- Check the current version installed
- If version is below 2.0.0, navigate to Plugins > Add New > Upload Plugin or check for an update notification
- Update the plugin to version 2.0.0 or latest available version
- Verify the update was successful and the plugin is functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Pro Mime Types
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32502 — 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-32502 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