CVE-2024-52421
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 wp-buy WP Popup Window Maker easy-popup-lightbox-maker allows Stored XSS.This issue affects WP Popup Window Maker: from n/a through <= 2.0.
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 WP Popup Window Maker plugin allows attackers to craft malicious requests that, when triggered by an authenticated administrator, can inject stored XSS payloads into popup configurations. The lack of proper CSRF token validation on admin actions enables attackers to hijack authenticated sessions to persist malicious scripts.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 the Popup Window Maker plugin is installedNavigate to WordPress admin > Plugins and confirm 'Popup Window Maker' or similar is installed and activeAffected if Plugin is installed and active with no CSRF protection on admin actions
-
Identify the installed plugin versionIn WordPress admin > Plugins, find Popup Window Maker and note the version number displayedAffected if Version is within the affected range lacking CSRF protection
-
Confirm admin access to plugin settingsAccess the plugin's admin panel (usually under a Popup Maker menu item in the admin sidebar)Affected if Plugin admin interface is accessible to authenticated administrators
-
Inspect admin forms for CSRF tokensView the page source of the plugin's admin pages, specifically form submissions, and search for nonce fields (typically named '_wpnonce' or similar)Affected if Forms lack nonce/token validation on state-changing actions like saving popup configurations
-
Check if popup configurations accept user input without sanitizationCreate or edit a popup via the plugin and inspect how user-supplied data is handled in the popup settingsAffected if Plugin allows saving unsanitized user input that could be exploited for stored XSS
User is affected if the WP Popup Window Maker plugin is installed, lacks CSRF token validation on admin forms, and allows unsanitized user input in popup configurations.
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 nonces and token validation on all state-changing admin actions and form submissions; also apply proper output escaping on user-supplied data to prevent XSS execution.
- Consultation2.0 h
- Implementation4.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52421 — 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-2024-52421 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