CVE-2026-32430
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in IdeaBox Creations PowerPack Addons for Elementor powerpack-lite-for-elementor allows Stored XSS.This issue affects PowerPack Addons for Elementor: from n/a through <= 2.9.9.
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 Stored Cross-Site Scripting (XSS) vulnerability exists in PowerPack Addons for Elementor plugin versions up to 2.9.9. The plugin fails to properly sanitize user input before rendering it in web pages, allowing attackers to inject malicious JavaScript that executes when site visitors view compromised content.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify installed plugin versionNavigate to WordPress Admin > Plugins > PowerPack Addons for Elementor and view the version number displayed, or check the plugin header in /wp-content/plugins/powerpack-addons-for-elementor/ via file systemAffected if version is 2.9.9 or lower
-
Confirm plugin is activeCheck if PowerPack Addons for Elementor appears in the list of active plugins in WordPress admin under Plugins > Installed PluginsAffected if plugin is active and version is within affected range
-
Inspect custom widget configurationsReview any PowerPack custom Elementor widgets that accept user input (such as info boxes, dual buttons, or content widgets) by examining the widget settings in the Elementor editor for each page using these widgetsAffected if any PowerPack widgets with user-editable text fields are in use on the site
-
Scan for stored XSS payloads in databaseQuery the wp_postmeta and wp_posts tables for suspicious script tags, javascript: URLs, or event handler attributes (onclick, onerror, onload) within PowerPack-related meta values or content containing PowerPack widget shortcodesAffected if malicious scripts are found stored in database entries associated with PowerPack widget content
You are affected if PowerPack Addons for Elementor is active at version 2.9.9 or lower and contains user-supplied content in its widgets that could harbor injected scripts.
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 PowerPack Addons for Elementor to the latest version beyond 2.9.9. Until a patch is available, review and sanitize all user inputs in the plugin using appropriate escaping functions (esc_html, esc_attr, wp_kses) before output.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32430 — 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-32430 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