LiveActive security incident?Get immediate response
CVE Record

CVE-2025-54694: WordPress Button Block Plugin plugin <= 1.2.0 - Cross Site Request Forgery (CSRF) Vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in bPlugins Button Block button-block allows Cross Site Request Forgery.This issue affects Button Block: from n/a through <= 1.2.0.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-54694 is a CSRF issue in the WordPress Button Block plugin by bPlugins, affecting versions through 1.2.0. A logged-in user could be tricked into causing a limited unintended change. The public sources rate this as medium severity, with low integrity impact and no reported confidentiality or availability impact.

Executive priority

Handle this through the normal WordPress vulnerability remediation queue, with priority for public sites and sites where many administrators stay logged in. It is not an emergency based on supplied evidence, but unresolved CSRF can still create business risk through unauthorized changes.

Technical view

The issue is CWE-352 Cross-Site Request Forgery in the button-block WordPress plugin. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N, score 4.3. Supplied sources do not identify the vulnerable endpoint, request, proof of concept, or a fixed version.

Likely exposure

Exposure is limited to WordPress sites that have bPlugins Button Block installed at version 1.2.0 or earlier. Sites not using this plugin are not indicated as affected by the supplied sources.

Exploitation context

The sources do not report active exploitation, and the CVE is not listed as KEV. Exploitation requires user interaction, consistent with CSRF, but the supplied evidence does not describe a specific attack path.

Researcher notes

Public detail is sparse. The supplied bundle confirms affected product, version range, CWE, CVSS, and Patchstack reference, but not the vulnerable action, nonce behavior, proof of concept, exploit maturity, or remediation version. Treat validation as inventory and vendor-guidance confirmation rather than exploit reproduction.

Mitigation direction

  • Inventory WordPress sites for the button-block plugin and version.
  • Check vendor, WordPress plugin, or Patchstack guidance for a fixed release.
  • Update the plugin if a fixed version is available.
  • Disable or remove the plugin if no acceptable fix is available.
  • Review recent administrative changes for unexpected plugin-related activity.

Validation and detection

  • Confirm whether each WordPress site has Button Block installed.
  • Verify installed versions are greater than 1.2.0 when vendor guidance confirms a fix.
  • Document sites where the plugin remains enabled without a confirmed fix.
  • Review WordPress administrative logs for unexpected content or settings changes.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-54694 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2025-54694Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
bPluginsButton Blockbutton-block, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.