CVE-2025-28981
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 Soli WP Mail Options wp-mail-options allows Stored XSS.This issue affects WP Mail Options: from n/a through <= 0.2.3.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the WP Mail Options WordPress plugin allows attackers to inject malicious JavaScript through Stored XSS by tricking authenticated administrators into submitting crafted requests. The lack of CSRF tokens enables attackers to forge administrative actions.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP Mail Options plugin is installedNavigate to WordPress admin > Plugins and locate 'WP Mail Options' in the installed plugins listAffected if Plugin is installed and active
-
Identify installed plugin versionClick on 'View details' or check the plugin header in wp-content/plugins/wp-mail-options/ folder for the 'Version' fieldAffected if Installed version falls within the vulnerable version range (compare your version to the affected releases)
-
Inspect plugin for CSRF nonce implementationOpen the main plugin PHP file (wp-mail-options.php) and search for 'wp_nonce_field', 'wp_nonce', 'check_admin_referer', or 'check_ajax_referer' function callsAffected if No nonce functions are found in form handling or admin action code
-
Check admin menu pages for nonce verificationReview all functions handling admin POST/GET requests (look for 'admin_post_', 'add_action' hooks with admin pages) and verify they call nonce verification functionsAffected if Admin action handlers do not validate CSRF tokens before processing requests
-
Examine form output for nonce fieldsLocate all HTML forms in the plugin (search for '<form') and verify each includes a hidden nonce field (input type='hidden' name='_wpnonce' or similar)Affected if Plugin forms lack hidden nonce token fields
A user is affected if WP Mail Options is installed, the version is within the vulnerable range, and the plugin code lacks CSRF token (nonce) validation on its forms and admin actions.
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 dataImplement anti-CSRF tokens (nonces) on all forms and admin actions, add proper input sanitization and output encoding for all user-supplied values, and update to a patched version of the plugin when available.
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28981 — 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-28981 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