dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-4655

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The Element Pack Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the SVG Image Widget in versions up to and including 8.4.2. This is due to insufficient input sanitization and output escaping on SVG content fetched from remote URLs in the render_svg() function. The function fetches SVG content using wp_safe_remote_get() and then directly echoes it to the page without any sanitization, only applying a preg_replace() to add attributes to the SVG tag which does not remove malicious event handlers. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary JavaScript in SVG files that will execute whenever a user accesses a page containing the malicious widget.

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 confidence

The Element Pack Addons plugin's SVG Image Widget fetches SVG content from remote URLs via wp_safe_remote_get() and outputs it directly in the render_svg() function without proper sanitization. The only processing is a preg_replace() that adds attributes to the SVG tag but fails to remove malicious event handlers (like onload, onerror), allowing stored XSS.

MitigationUpdate the plugin to a version beyond 8.4.2 which includes proper SVG sanitization. Until an update is available, disable the SVG Image Widget or restrict contributor-level publishing capabilities.

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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 Element Pack Addons plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Element Pack Addons' or 'Element Pack' in the plugin list. Note the installed version number shown.
    Affected if The plugin is installed and active
  2. Verify the SVG Image Widget is in use
    Check your pages, posts, or widget areas for any instance of the Element Pack SVG Image Widget. This can be done by searching for 'svg' or 'Element Pack' in the page editor, or by searching your database for posts containing the widget shortcode or block.
    Affected if Any page, post, or widget area contains an active SVG Image Widget instance
  3. Identify remote SVG sources configured in the widget
    Edit each page/post containing the SVG Image Widget and examine the widget settings. Look for a URL field that specifies a remote SVG source. Note the configured URLs.
    Affected if The SVG Image Widget is configured to fetch SVG content from a remote URL rather than uploading directly
  4. Inspect stored SVG content for malicious handlers
    If remote SVG URLs are configured, examine the actual SVG files being fetched (visit the URL directly in a browser and view the source). Look for event handler attributes such as onload, onerror, onclick, onmouseover, onfocus, or script tags within the SVG markup.
    Affected if The fetched SVG content contains any event handler attributes (onload, onerror, etc.) or script elements that could execute JavaScript

Your environment is affected if the Element Pack Addons plugin is installed with the SVG Image Widget active and configured to fetch remote SVG content that contains event handler attributes or script elements.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a version beyond 8.4.2 which includes proper SVG sanitization. Until an update is available, disable the SVG Image Widget or restrict contributor-level publishing capabilities.

Recommended fix Moderate confidence

Version after 8.4.2 (latest stable release)

  1. Upgrade the Element Pack Addons for Elementor plugin to the latest available version from the WordPress plugin repository
  2. After upgrading, verify that the SVG Image Widget functions correctly on your pages
  3. Review existing pages using the SVG Image Widget to ensure no malicious SVG content was previously injected
  4. Consider implementing additional content security policy (CSP) headers as a defense-in-depth measure

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4655 — 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-2026-4655 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