Wp TopbarWordPress extension · Wp Topbar Project
CVE-2023-23680
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 Bob Goetz WP-TopBar plugin <= 5.36 versions.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the WP-TopBar WordPress plugin versions 5.36 and below allows attackers to potentially perform unintended administrative actions by tricking authenticated users into clicking malicious links or visiting crafted pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp TopbarWordPress extension
<= 5.36CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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-TopBar plugin is installedLog in to WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'WP-TopBar' or 'Wp Topbar Project Wp Topbar' in the list of active pluginsAffected if WP-TopBar plugin appears in the installed plugins list
-
Check installed WP-TopBar versionIn WordPress admin, go to Plugins > Installed Plugins, locate WP-TopBar, and note the version number displayed under the plugin name. Alternatively, check the plugin's main PHP file header for the Version fieldAffected if The installed version is 5.36 or any version lower than 5.36
-
Identify state-changing plugin featuresAccess WP-TopBar settings by navigating to Settings > Top Bar in the WordPress admin. Look for any forms that modify plugin configuration, such as saving bar settings, creating or editing bars, or updating display optionsAffected if The plugin has active configurations and forms that modify settings (even if currently using default values)
-
Inspect for CSRF token validation (optional manual check)View the page source of the WP-TopBar settings pages. Right-click > View Page Source, then search for 'nonce' or 'wpnonce' in the HTML. Check if form submissions include a security tokenAffected if Forms submitting to wp-admin/admin-post.php or similar endpoints lack nonce/token fields in the HTML
You are affected if the WP-TopBar plugin is installed and the installed version is 5.36 or lower, as the plugin lacks proper CSRF protection for administrative actions in these versions.
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 WP-TopBar plugin to the latest version (5.37 or higher) which should include proper anti-CSRF token validation for state-changing operations.
Fix this in Wp Topbar
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23680 — 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-2023-23680 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