CVE-2025-24711
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 Popup Box popup-box allows Cross Site Request Forgery.This issue affects Popup Box: from n/a through <= 3.2.4.
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 Popup Box WordPress plugin (versions <= 3.2.4) allows remote attackers to trick authenticated administrators into performing unintended state-changing actions like modifying popup configurations via forged 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 Wow-Company Popup Box plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Popup Box' by Wow-Company, or check the /wp-content/plugins/ directory for a folder named 'popup-box' or similar Wow-Company popup plugin folderAffected if The plugin is not found or not active - no CSRF risk from this specific plugin
-
Check the installed plugin versionIn WordPress admin Plugins list, find the Popup Box plugin and note the version number displayed, or open the main plugin PHP file and look for the 'Version' header in the plugin commentsAffected if Version is 3.2.4 or lower - vulnerable to this CSRF flaw
-
Identify state-changing admin actionsReview the plugin settings pages in the WordPress admin panel (typically under Wow-Company or Popup Box menu) to see what configuration options exist - look for forms that create, edit, delete, or toggle popupsAffected if Popup configurations exist that can be modified - these represent the state-changing actions a CSRF attack could target
-
Inspect plugin code for nonce verification absenceExamine the plugin PHP files handling form submissions and AJAX actions (often in main plugin file or includes/admin folder). Search for 'wp_nonce_field', 'check_admin_referer', 'check_ajax_referer', or 'verify_nonce' around form processing code. Look for state-changing functions that lack these verification callsAffected if Form handlers or AJAX endpoints processing configuration changes do not validate nonces - the plugin is vulnerable to CSRF exploitation
A user is affected if the Wow-Company Popup Box plugin is installed with version 3.2.4 or lower and handles admin configuration changes without WordPress nonce verification, allowing forged requests to modify popup settings.
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 dataAdd WordPress nonce verification to all form submissions and AJAX actions within the plugin, ensuring state-changing requests validate a unique token server-side before execution.
- Consultation1.0 h
- Implementation3.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 $1,952.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24711 — 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-24711 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