CVE-2025-24720
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 Sticky Buttons sticky-buttons allows Cross Site Request Forgery.This issue affects Sticky Buttons: from n/a through <= 4.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 · high confidenceCross-Site Request Forgery (CSRF) vulnerability in the Wow-Company Sticky Buttons WordPress plugin allows attackers to trick authenticated administrators into performing unintended state-changing actions (such as modifying button configurations) by exploiting the lack of anti-CSRF token validation on sensitive operations.
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.
-
Confirm plugin installationNavigate to WordPress admin dashboard > Plugins and verify if 'Sticky Buttons' by Wow-Company is installed and activeAffected if The plugin is installed and active on the WordPress site
-
Locate plugin admin filesAccess the wp-content/plugins/sticky-buttons or similar directory via file manager or FTP, and identify PHP files handling admin actions (typically files with 'admin', 'settings', or 'option' in the name)Affected if Plugin files exist and contain code for handling state-changing operations
-
Inspect AJAX action handlersSearch PHP files for 'add_action' hooks on 'wp_ajax_' and 'wp_ajax_nopriv_' to find all AJAX endpoints, then verify if each includes nonce verification using wp_verify_nonce(), check_ajax_referer(), or wp_nonce_field()Affected if AJAX actions exist without nonce validation before processing requests
-
Check form submissions for nonce fieldsExamine PHP files that generate admin forms (look for 'admin_post_', 'add_settings_section', or form tags) and verify that each form includes a nonce field via wp_nonce_field() or similar, and that the receiving handler validates itAffected if Forms exist that submit to admin-post.php or similar handlers without nonce validation
-
Verify state-changing operationsIdentify functions that modify plugin settings or button configurations (look for 'update_option', 'insert', 'update', 'delete' database operations) and confirm they are preceded by nonce validation checksAffected if Data modification functions are called without prior nonce verification
The site is affected if the Wow-Company Sticky Buttons plugin is installed and any of its admin actions, AJAX endpoints, or form handlers lack WordPress nonce validation before performing state-changing operations.
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 WordPress nonces (anti-CSRF tokens) on all form submissions and AJAX actions that modify plugin settings, and verify these nonces server-side before processing any state-changing requests.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24720 — 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-24720 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