CVE-2025-12406
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 Project Honey Pot Spam Trap plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.1. This is due to missing or incorrect nonce validation on the printAdminPage() function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 Project Honey Pot Spam Trap WordPress plugin versions up to 1.0.1 lacks CSRF protection (nonce validation) in its printAdminPage() function, allowing unauthenticated attackers to forge administrative requests that can modify plugin settings and inject malicious JavaScript.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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.
-
Verify Project Honey Pot Spam Trap plugin is installedNavigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and locate Project Honey Pot Spam Trap in the listAffected if The plugin appears in the installed plugins list
-
Check the installed plugin versionIn the Plugins list, click on the plugin and view the version number displayed in the plugin details, or check the plugin's main PHP file header for the Version fieldAffected if The version listed is 1.0.1 or earlier
-
Examine the printAdminPage() function for nonce implementationAccess the plugin source code (typically in wp-content/plugins/project-honey-pot-spam-trap/ or similar path), locate the printAdminPage() function, and search for wp_nonce_field, wp_verify_nonce, or check_admin_referer calls within that function and any forms it rendersAffected if The function contains no nonce verification calls (wp_nonce_field, wp_verify_nonce, or check_admin_referer are absent)
-
Inspect admin forms for nonce field presenceView the HTML source of the plugin's admin settings page (the page that displays the plugin configuration options), and search for an input field with name containing '_nonce' or a hidden field generated by wp_nonce_fieldAffected if No nonce hidden fields are present in the plugin's admin settings forms
A user is affected if the Project Honey Pot Spam Trap plugin is installed at version 1.0.1 or earlier AND the printAdminPage() function or its forms lack nonce verification code.
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 the plugin to version 1.0.2 or later which includes proper nonce validation; alternatively, add wp_nonce_field() to admin forms and verify with wp_verify_nonce() before processing settings.
- 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-2025-12406 — 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-12406 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