dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14339

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The weMail - Email Marketing, Lead Generation, Optin Forms, Email Newsletters, A/B Testing, and Automation plugin for WordPress is vulnerable to unauthorized form deletion in all versions up to, and including, 2.0.7. This is due to the `Forms::permission()` callback only validating the `X-WP-Nonce` header without checking user capabilities. Since the REST nonce is exposed to unauthenticated visitors via the `weMail` JavaScript object on pages with weMail forms, any unauthenticated user can permanently delete all weMail forms by extracting the nonce from the page source and sending a DELETE request to the forms endpoint.

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 confidence

The weMail WordPress plugin versions up to 2.0.7 have a broken access control vulnerability in the REST API endpoint for form deletion. The Forms::permission() callback only validates the X-WP-Nonce header without checking user capabilities, and this nonce is exposed to unauthenticated visitors via the weMail JavaScript object on pages displaying forms. This allows any unauthenticated user to permanently delete all weMail forms by extracting the nonce and sending a DELETE request to the forms endpoint.

MitigationUpdate to version 2.0.8 or later, which should add proper capability checks in the Forms::permission() callback and stop exposing the REST nonce to unauthenticated users.

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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed weMail plugin version
    In WordPress admin, go to Plugins > weMail, or check the plugin header in wp-content/plugins/mailwizz/mailwizz.php for the Version field, or use WP-CLI: wp plugin list --name=mailwizz --format=table
    Affected if Version is 2.0.7 or lower (the vulnerability exists up to 2.0.7)
  2. Inspect weMail JavaScript for exposed nonce
    Visit any page on the site that displays a weMail form (check pages with weMail embed code or shortcode). View page source (Ctrl+U or right-click > View Page Source). Search for 'wpApiSettings' or a weMail-specific JavaScript object (such as weMailConfig or similar) and look for a 'nonce' or 'restNonce' property that is visible in the HTML
    Affected if A REST API nonce is present in the frontend JavaScript visible to unauthenticated visitors (it should not be exposed to non-admins)
  3. Test form deletion REST API endpoint accessibility
    Send a DELETE request to the weMail forms endpoint (typically /wp-json/mailwizz/v1/forms/ with an extracted nonce in the X-WP-Nonce header). Use a tool like curl: curl -X DELETE https://yoursite.com/wp-json/mailwizz/v1/forms/<id> -H 'X-WP-Nonce: <extracted_nonce>'
    Affected if The server accepts the DELETE request and processes it without requiring authentication beyond the nonce (vulnerable behavior)
  4. Verify Forms::permission() lacks capability check
    If you have code access, examine the file containing the Forms::permission() method (usually in includes/classes/Forms.php or similar). Look for a call to current_user_can() or a capability check. The method should only be checking the nonce, not verifying the user has 'manage_options' or 'delete_posts' capabilities
    Affected if The permission callback validates only the nonce header and does not call current_user_can() or similar capability verification

Your environment is affected if weMail plugin version is 2.0.7 or lower AND the REST API nonce is exposed in frontend JavaScript to unauthenticated visitors, allowing form deletion without proper capability verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 2.0.8 or later, which should add proper capability checks in the Forms::permission() callback and stop exposing the REST nonce to unauthenticated users.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14339 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14339 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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