dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-28923

HIGH · 7.1 CVSS v3.1 Published 2025-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in philippe No Disposable Email no-disposable-email allows Stored XSS.This issue affects No Disposable Email: from n/a through <= 2.5.1.

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 confidence

A CSRF vulnerability in the No Disposable Email WordPress plugin (versions up to 2.5.1) allows attackers to craft malicious requests that result in Stored XSS. Attackers can exploit the lack of anti-CSRF tokens to inject persistent malicious scripts into email domain configurations that execute when users view affected admin pages or frontend displays.

MitigationImplement anti-CSRF nonces for all state-changing actions and apply proper output escaping for all user-supplied data before rendering to prevent XSS execution.

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 checks

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

  1. Verify No Disposable Email plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or use WP-CLI: wp plugin list --search='no-disposable-email'
    Affected if The plugin appears in the list of installed plugins and is activated
  2. Check the installed plugin version
    In WordPress admin, click on the plugin from the plugins list to view version details, or inspect the main plugin file header in wp-content/plugins/no-disposable-email/ for the 'Version' comment
    Affected if The version number is 2.5.1 or lower (any version up to and including 2.5.1)
  3. Inspect email domain configuration settings
    Navigate to the plugin settings page in WordPress admin (usually under Settings > No Disposable Email or similar), and examine any fields related to email domain whitelists or blacklists
    Affected if Configuration fields accept user input without visible nonce verification, or contain unexpected/suspicious domain entries that you did not add
  4. Review stored options in database
    Query the wp_options table for option_name values related to this plugin (such as nde_*, no disposable email, or similar), or use WP-CLI: wp option list --search='%nde%' or wp option list --search='%disposable%'
    Affected if Stored option values contain encoded JavaScript, script tags, or other unexpected content that resembles exploit payloads
  5. Examine admin pages for injected scripts
    View the source HTML of the plugin settings page and any frontend pages that display email domains, looking for unexpected script tags, event handlers, or encoded content
    Affected if Rendered HTML contains script tags, javascript: URIs, or XSS vectors in locations where email domain data is displayed

If the No Disposable Email plugin is installed at version 2.5.1 or lower and contains unexpected content in domain configuration fields or displays unescaped content in the admin interface, the environment is affected by this CVE.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF nonces for all state-changing actions and apply proper output escaping for all user-supplied data before rendering to prevent XSS execution.

Recommended fix Moderate confidence

Version 2.5.2 or higher (check WordPress plugin repository for latest fixed release)

  1. Check the WordPress plugin repository or the plugin vendor's official website for the No Disposable Email plugin (no-disposable-email) to identify if version 2.5.2 or higher is available
  2. If a fixed version (2.5.2 or higher) is available, update the plugin through the WordPress admin dashboard or via wp-cli: wp plugin update no-disposable-email
  3. After updating, verify the CSRF protection is properly implemented by confirming nonce verification or token validation is in place for all form submissions and admin actions
  4. Test the admin interface to ensure the plugin functionality remains intact after the update
  5. Review WordPress security best practices for CSRF protection to ensure future updates maintain proper safeguards

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-28923 — 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-28923 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