CVE-2025-12412
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 Top Bar Notification plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.12. This is due to missing or incorrect nonce validation on th tbn_ajax_add() function. This makes it possible for unauthenticated attackers to update the plugin's 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 · moderate confidenceThe Top Bar Notification WordPress plugin (versions up to 1.12) lacks proper nonce validation in its tbn_ajax_add() function, enabling cross-site request forgery attacks. Unauthenticated attackers can forge administrator requests to modify plugin settings and inject malicious scripts via social engineering.
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.
-
Locate the Top Bar Notification pluginCheck your WordPress installation's wp-content/plugins/ directory for a folder named 'top-bar-notification' or similar variant containing 'top-bar' and 'notification'Affected if The plugin folder exists in the plugins directory
-
Identify the installed versionOpen the main plugin PHP file (often named top-bar-notification.php or similar) and locate the 'Version:' header in the plugin comment block, or check the plugin's readme.txt fileAffected if The version number is 1.12 or lower (including any 1.x.x version up to 1.12)
-
Locate the vulnerable tbn_ajax_add() functionSearch the plugin files for the function definition 'function tbn_ajax_add()' using grep or a file search in the plugin directoryAffected if The function exists in the plugin code
Your environment is affected if the Top Bar Notification plugin is installed with version 1.12 or lower and contains the tbn_ajax_add() function accessible to unauthenticated users.
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 patched version if available; otherwise, add nonce verification to tbn_ajax_add() using wp_verify_nonce() and implement proper capability checks for admin actions.
Top Bar Notification version 1.13 or later
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate 'Top Bar Notification' plugin
- Check if current version is 1.12 or below
- If vulnerable, click 'Update Now' to update to the latest version
- Verify the plugin updated to version 1.13 or higher
- Clear any site caches if caching plugins are in use
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12412 — 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-12412 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