CVE-2024-34367
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 Popup Box Team Popup box allows Cross-Site Scripting (XSS).This issue affects Popup box: from n/a through 4.1.2.
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 confidenceA CSRF vulnerability in the Popup Box plugin allows authenticated administrators to be tricked into performing actions that result in stored XSS. Attackers can craft malicious requests that, when triggered by an admin session, inject XSS payloads into popup configurations.
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 Popup Box plugin installationNavigate to WordPress admin > Plugins and locate the Popup Box plugin in the list, or check for the /wp-content/plugins/popup-box/ directory via file manager or FTPAffected if Popup Box plugin is present in the WordPress installation
-
Determine installed plugin versionIn WordPress admin > Plugins, click on the Popup Box plugin to view its version number, or read the main plugin file (popup-box.php) and locate the 'Version' header commentAffected if The installed version is older than the version that includes the CSRF fix (the patched version)
-
Confirm plugin is activeCheck the Plugins list in WordPress admin - the plugin must be both installed AND active for the vulnerability to be exploitableAffected if Popup Box plugin is active on the site
-
Inspect popup configurations for injected scriptsNavigate to the Popup Box plugin settings in WordPress admin (typically under a 'Popups' or 'Popup Box' menu). Review all saved popup configurations for any unexpected JavaScript tags, event handlers (onclick, onerror, onload), or suspicious URL patterns in fields that accept HTML or JavaScriptAffected if Popup configurations contain unrecognized JavaScript code or XSS payloads that were not intentionally added by your team
-
Verify admin action nonce protectionExamine the plugin source code (admin/*.php files) for state-changing actions (POST/GET requests that save, update, or delete data). Check if each action includes and validates a wp_nonce_field() or check_admin_referer() call before processingAffected if Admin actions lack proper nonce verification, allowing CSRF attacks to succeed
A user is affected if the Popup Box plugin is installed, active, running an unpatched version, and admin actions lack CSRF protection - resulting in potential XSS injection 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 dataUpdate the Popup Box plugin to the latest version. If no update is available, disable the plugin until a patch is released. Implement anti-CSRF tokens (nonces) on all state-changing admin actions.
- 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-2024-34367 — 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-34367 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