dbcve.org
Jazz PopupsWordPress extension · Crudlab

CVE-2023-32965

MEDIUM · 6.1 CVSS v3.1 Published 2023-07-18
Fix available
A fix is available. Upgrade to after 1.8.7 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in CRUDLab Jazz Popups plugin <= 1.8.7 versions.

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 confidence

Unauthenticated reflected Cross-Site Scripting (XSS) vulnerability in the CRUDLab Jazz Popups WordPress plugin versions 1.8.7 and below allows attackers to inject malicious JavaScript through unsanitized user input that gets reflected back in the HTTP response.

MitigationUpdate the Jazz Popups plugin to the latest available version; if no patched version exists, disable or remove the plugin until a fix is released.

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
Affected:<= 1.8.7

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Jazz Popups plugin is installed
    Navigate to WordPress admin dashboard under Plugins > Installed Plugins, or inspect the wp-content/plugins directory for a folder containing 'jazz-popups' or 'crudlab-jazz-popups'.
    Affected if The plugin is present in the plugins directory or listed in the WordPress admin.
  2. Check installed plugin version
    In WordPress admin, view the plugin details to see the version number. Alternatively, open the plugin's main PHP file or readme.txt in wp-content/plugins/jazz-popups/ and locate the 'Version:' header field.
    Affected if The version listed is 1.8.7 or any version number lower than 1.8.7.
  3. Verify plugin is active
    In WordPress admin under Plugins > Installed Plugins, check if Jazz Popups shows as 'Active' under the plugin status column.
    Affected if The plugin is currently activated on the WordPress site.
  4. Identify exposed endpoint (optional verification)
    Review the plugin files (typically in the main plugin PHP file) to locate any HTTP parameter handling that reflects user input back into the response without sanitization. Common parameters to test include query string parameters or form inputs processed by the plugin.
    Affected if The plugin processes and reflects user-supplied input in HTTP responses without proper output encoding.

You are affected if the Jazz Popups plugin is installed, active, and running version 1.8.7 or lower.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.8.7
Interim mitigation

Update the Jazz Popups plugin to the latest available version; if no patched version exists, disable or remove the plugin until a fix is released.

Recommended fix Moderate confidence

Upgrade to Jazz Popups version 1.8.8 or later (the first version containing the security fix)

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. 3. Locate the 'Jazz Popups' plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Verify the plugin has been updated to a version higher than 1.8.7
  6. 6. Test that the Jazz Popups functionality works correctly after the update
  7. 7. Clear any caching plugins or server-side caches

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jazz Popups Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32965 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-32965 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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