Button BlockWordPress extension · Bplugins
CVE-2025-22787
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 · uneditedMissing Authorization vulnerability in bPlugins Button Block button-block allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Button Block: from n/a through <= 1.1.5.
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 confidenceMissing Authorization vulnerability in the bPlugins Button Block WordPress plugin (version <= 1.1.5) allows unauthenticated or low-privilege users to access functionality that should be constrained by Access Control Lists (ACLs). The specific privileged action is not detailed, but the CVSS 8.8 indicates significant impact requiring low attack complexity.
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
Button BlockWordPress extension
< 1.1.6CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Locate the bPlugins Button Block plugin in your WordPress installationCheck the /wp-content/plugins/ directory for a folder named 'button-block' or 'bplugins-button-block', or use WP-CLI: wp plugin list --name='*button*'Affected if The plugin folder exists in the WordPress plugins directory
-
Determine the installed version of the pluginRead the main plugin file header (usually button-block.php or index.php in the plugin folder) and look for 'Version:' in the plugin comments, or run: wp plugin get button-block --format=jsonAffected if The reported version is 1.1.5 or lower (any version below 1.1.6)
-
Verify the plugin is active on your siteCheck WordPress admin under Plugins > Installed Plugins, or run: wp plugin is-active button-blockAffected if The plugin is activated and running on the WordPress site
You are affected if bPlugins Button Block plugin is installed, active, and running version 1.1.5 or lower, exposing privileged functionality to unauthenticated or low-privilege 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 · scoped1.1.6
Update the Button Block plugin to a version newer than 1.1.5 once available, or disable the plugin until a patched version is released.
Button Block version 1.1.6
- Backup your WordPress site database and files before making any changes
- Update the Button Block plugin to version 1.1.6 or later through the WordPress admin dashboard (Plugins > All Plugins > Button Block > Update)
- Alternatively, update via WP-CLI: wp plugin update button-block
- After updating, verify the plugin version shows 1.1.6 or higher in the Plugins list
- Test that the button block functionality works as expected in your content
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Button Block
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22787 — 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-22787 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