CVE-2026-1447
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 Cross-Site Request Forgery in all versions up to, and including, 1.19.2. This is due to missing nonce validation on the create_or_update_note function. This makes it possible for unauthenticated attackers to create or update contact notes via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Due to missing sanitization and escaping this can lead to stored Cross-Site Scripting.
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 is vulnerable to CSRF in versions up to 1.19.2 due to missing nonce validation on the create_or_update_note function. This allows unauthenticated attackers to trick administrators into creating or updating contact notes via forged requests. The lack of input sanitization and output escaping on the note content also enables stored XSS attacks.
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
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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.
-
Confirm Mail Mint plugin is installedNavigate to WordPress admin dashboard > Plugins, or inspect the /wp-content/plugins/mail-mint directory via file systemAffected if Mail Mint plugin is not present in the installation
-
Check the installed version of Mail MintIn WordPress admin, go to Plugins > Installed Plugins > Mail Mint and view the version number. Alternatively, read the main plugin file header in /wp-content/plugins/mail-mint/mail-mint.phpAffected if The installed version is below 1.19.2 (versions 1.x.x through 1.19.1 are affected)
-
Verify the plugin is activeIn WordPress admin > Plugins, check if Mail Mint shows as ActiveAffected if The plugin is active and the version is below 1.19.2
-
Check for admin action accessibilityThe vulnerable function create_or_update_note is an admin AJAX action. Inspect network traffic when an admin accesses the dashboard, or review plugin code for the function locationAffected if The create_or_update_note function is accessible without nonce verification (requires code review or penetration testing to confirm)
You are affected if Mail Mint plugin is installed, active, and running a version below 1.19.2, allowing unauthenticated attackers to perform CSRF attacks leading to stored XSS via the create_or_update_note function.
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 · scopedUpdate to version 1.19.2 or later (or the latest patched version). If no update is available, remove the plugin until a patch is released.
Mail Mint version 1.19.3 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the Mail Mint plugin
- Check if an update is available and update to version 1.19.3 or later
- Alternatively, you can download the latest version from the WordPress plugin repository and upload it manually
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1447 — 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-2026-1447 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