Security readout for executives and security teams
Plain-English summary
CVE-2025-24713 is a medium-severity CSRF issue in the WordPress Button Generator – easily Button Builder plugin through version 3.1.1. It could let an attacker cause unwanted plugin-related actions if a user is tricked while authenticated. The source bundle does not identify a fixed version or detailed mitigation.
Executive priority
Treat as a normal-priority remediation for WordPress estates, not an emergency based on available evidence. Focus first on externally important sites, administrator-heavy workflows, and environments where plugin changes could affect customer-facing content.
Technical view
The record maps this to CWE-352 with CVSS 3.1 score 5.4: network reachable, low complexity, no attacker privileges, user interaction required, low integrity and availability impact, no confidentiality impact. The affected package is button-generation for Wow-Company Button Generator – easily Button Builder through 3.1.1.
Likely exposure
Exposure is limited to WordPress sites with the Button Generator – easily Button Builder plugin installed at version 3.1.1 or earlier. Sites not using this plugin are not indicated as affected by the provided sources.
Exploitation context
The CVE is not listed as KEV in the bundle, and no cited source here states active exploitation. CSRF risk depends on an authenticated user interacting with attacker-controlled content. The exact vulnerable action is not described in the supplied evidence.
Researcher notes
The public bundle confirms CSRF classification, affected plugin, affected version range, and CVSS vector. It does not provide proof-of-concept detail, exact vulnerable endpoint, fixed version, or active exploitation evidence. Avoid assuming impact beyond low integrity and availability effects.
Mitigation direction
Inventory WordPress sites for the button-generation plugin.
Check vendor, WordPress, or Patchstack guidance for a fixed release.
Disable or remove the plugin if no safe version is available.
Limit administrative browsing from authenticated WordPress sessions.
Prioritize sites where untrusted users can target administrators.
Validation and detection
Confirm installed plugin name and version on each WordPress site.
Flag Button Generator – easily Button Builder versions 3.1.1 or earlier.
Review plugin and WordPress audit logs for unexpected changes.
Check whether compensating CSRF protections are documented by the vendor.
Reassess after vendor or Patchstack publishes remediation details.
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.
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.
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.
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.