CVE-2026-39597
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 · uneditedUnauthenticated Cross Site Scripting (XSS) in WPZOOM Addons for Elementor <= 1.3.4 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 confidenceAn unauthenticated Cross Site Scripting (XSS) vulnerability exists in the WPZOOM Addons for Elementor plugin versions 1.3.4 and below. Attackers can inject malicious JavaScript code through unsanitized user inputs, potentially compromising other users' sessions or performing actions on their behalf.
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 WPZOOM Addons for Elementor is installedCheck your WordPress plugins directory or navigate to Plugins > Installed Plugins in the WordPress admin dashboard and look for 'WPZOOM Addons for Elementor' in the list of installed pluginsAffected if plugin is not found in the installation - not affected
-
Determine the installed plugin versionIn the WordPress admin, go to Plugins > Installed Plugins, find WPZOOM Addons for Elementor, and view the version number displayed beneath the plugin nameAffected if version number cannot be determined or is not visible - verification incomplete
-
Compare version to affected rangeCompare the installed version number you found to the affected range: versions 1.3.4 and below are vulnerableAffected if installed version is 1.3.4 or lower - environment is affected
-
Confirm plugin is activeIn WordPress admin at Plugins > Installed Plugins, verify the WPZOOM Addons for Elementor plugin shows as 'Active' rather than 'Inactive'Affected if plugin is active and version is 1.3.4 or below - directly affected by this vulnerability
Your environment is affected if WPZOOM Addons for Elementor is installed, currently active, and running version 1.3.4 or below.
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.
dbcve · scopedUpdate WPZOOM Addons for Elementor to the latest version immediately. If updates are unavailable, disable the plugin until a patch is released.
Upgrade to the latest version of WPZOOM Addons for Elementor (version 1.3.5 or higher)
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find WPZOOM Addons for Elementor in the plugin list
- Check if an update is available and update to the latest version
- Alternatively, download the latest version from the WordPress plugin repository or WPZOOM official source and upload/replace the existing plugin
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2026-39597 — 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-2026-39597 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