CVE-2025-24713
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 Wow-Company Button Generator – easily Button Builder button-generation allows Cross Site Request Forgery.This issue affects Button Generator – easily Button Builder: from n/a through <= 3.1.1.
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 Wow-Company Button Generator WordPress plugin allows authenticated administrators to be tricked into generating or modifying button configurations via maliciously crafted requests.
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
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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 plugin installation and activation statusLog into WordPress admin panel, navigate to Plugins > Installed Plugins, and locate 'Wow-Company Button Generator' or 'Button Generator - Best Button Generator' in the listAffected if The plugin is installed and active in the WordPress environment
-
Identify installed plugin versionIn WordPress plugins list, click on the plugin name to view details, or access the plugin files via FTP/file manager and read the main PHP file header for the 'Version' tagAffected if The installed version falls within any known vulnerable version range (compare to official WordPress repository release notes)
-
Inspect form handlers for nonce verificationAccess plugin directory (wp-content/plugins/button-generator-wow or similar), locate PHP files handling form submissions (typically in admin/class-*.php or includes/*.php), search for 'wp_nonce_field' or 'wp_verify_nonce' function calls within form processing codeAffected if Form handling code lacks nonce verification logic (missing wp_nonce_field in forms and missing wp_verify_nonce in processing handlers)
-
Check AJAX endpoint protectionLocate AJAX action handlers in plugin files (search for 'add_action.*wp_ajax'), examine whether each handler verifies nonce via 'check_ajax_referer' or 'wp_verify_nonce' before processing requestsAffected if AJAX endpoints do not validate nonces before executing button configuration changes
A user is affected if the Wow-Company Button Generator plugin is installed and its version lacks anti-CSRF nonce protection in form submissions and AJAX endpoints.
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 dataImplement anti-CSRF nonce verification on all form submissions and AJAX endpoints within the plugin, add Origin/Referer header validation, and update to the patched version when available.
- Consultation2.0 h
- Implementation6.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 $3,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24713 — 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-24713 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