CVE-2025-11967
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 Mail Mint plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the process_contact_attribute_import function in all versions up to, and including, 1.18.10. This makes it possible for authenticated attackers, with Administrator-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.
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 Mail Mint WordPress plugin fails to validate file types in the process_contact_attribute_import function, allowing authenticated administrators to upload arbitrary files including executable code. This arbitrary file upload vulnerability enables remote code execution on affected servers.
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
- 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 Mail Mint plugin is installedIn WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'Mail Mint' in the list. Alternatively, check the /wp-content/plugins/mail-mint directory exists on the server.Affected if Mail Mint plugin is not found in the plugins list or directory
-
Determine installed Mail Mint versionIn WordPress admin, go to Plugins > Installed Plugins > Mail Mint and look for the version number displayed. Alternatively, check the main plugin file header in /wp-content/plugins/mail-mint/mail-mint.php for the Version field.Affected if Version is present and is lower than 1.18.11, or version cannot be determined (plugin may be outdated or corrupted)
-
Check WordPress user roles for administrator accountsIn WordPress admin, go to Users > All Users and review the listed roles. Confirm which accounts have Administrator role. The vulnerability is exploitable by authenticated administrators.Affected if There are one or more administrator-level accounts on the WordPress site
-
Inspect upload directories for unexpected filesCheck the /wp-content/uploads/ directory and subdirectories for unfamiliar files with extensions such as .php, .phtml, .exe, .sh, or other executable extensions that were not intentionally uploaded by legitimate site operations.Affected if Unexpected executable files are found in upload directories, especially PHP files that do not belong to known themes or plugins
The environment is affected if Mail Mint plugin is installed with a version lower than 1.18.11 and administrator accounts exist on the site, making the arbitrary file upload vulnerability potentially exploitable.
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 Mail Mint plugin to version 1.18.11 or later to receive the file type validation fix. Restrict administrator-level access to trusted personnel only.
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11967 — 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-11967 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