Jazz PopupsWordPress extension · Crudlab
CVE-2023-32966
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 CRUDLab Jazz Popups leads to Stored XSS.This issue affects Jazz Popups: from n/a through 1.8.7.
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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability in the Jazz Popups WordPress plugin (versions up to 1.8.7) allows authenticated attackers to trick administrators into submitting malicious requests that result in Stored XSS. The lack of proper CSRF token validation on form submissions enables attackers to inject malicious scripts that persist in the database and execute when users view the affected popups.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Jazz PopupsWordPress extension
<= 1.8.7CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Check if Jazz Popups plugin is installedGo to WordPress Admin > Plugins and look for 'Jazz Popups' in the list, or check the file /wp-content/plugins/ for a folder named 'jazz-popups' or similarAffected if The plugin is installed and the version is 1.8.7 or lower
-
Verify the plugin versionIn WordPress Admin > Plugins, click on the Jazz Popups plugin to view its details, or read the version from the plugin's main PHP file header (typically in /wp-content/plugins/jazz-popups/ or similar folder name)Affected if Version is 1.8.7 or below (any version up to and including 1.8.7)
-
Check if plugin admin forms have CSRF protectionInspect the page source of the plugin's admin settings page (usually under a Jazz Popups menu item). Look for a hidden input field containing 'nonce' or '_wpnonce' in any form tags that submit popup configurationsAffected if Forms lack nonce/CSRF token fields, meaning the plugin does not validate anti-CSRF tokens on form submissions
-
Inspect database for suspicious popup contentQuery the WordPress database (via phpMyAdmin or wp-cli: wp db query "SELECT * FROM wp_posts WHERE post_type LIKE '%popup%' OR post_content LIKE '%<script%' OR post_content LIKE '%onerror=%'") to find any popup entries containing JavaScript tags or event handlersAffected if Popups exist in the database containing unsanitized script tags, event handlers (onerror, onload, etc.), or other XSS payloads
You are affected if the Jazz Popups plugin (version 1.8.7 or lower) is installed and active, its admin forms lack CSRF token validation, or suspicious XSS payload entries exist in the database.
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 tokens (nonces) on all form submissions and admin actions, and apply proper input sanitization and output encoding to prevent Stored XSS. Upgrade to the latest plugin version if available.
Fix this in Jazz Popups
Scoped from the published advisory
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32966 — 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-2023-32966 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