CVE-2026-4790
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 · uneditedThe Premium Addons for Elementor – Powerful Elementor Templates & Widgets plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'custom_svg' parameter in versions up to, and including, 4.11.70 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 confidenceThe Premium Addons for Elementor plugin versions up to 4.11.70 suffers from a stored XSS vulnerability in the 'custom_svg' parameter due to insufficient input sanitization and improper output escaping, allowing authenticated attackers with contributor-level or higher access to inject persistent malicious scripts.
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
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Verify Premium Addons for Elementor is installedNavigate to Plugins > Installed Plugins in WordPress admin and locate Premium Addons for Elementor, or check the plugin files for version information in the main plugin file headerAffected if the plugin is installed and the version is 4.11.70 or lower
-
Confirm installed version numberRead the version string from the plugin's main PHP file (typically premium-addons-for-elementor/includes/class-premium-addons-for-elementor.php) or from the WordPress plugins listAffected if the version is 4.11.70 or any version up to and including 4.11.70
-
Identify use of custom_svg parameterQuery the WordPress postmeta table for entries containing 'custom_svg' as a meta_key, or inspect Elementor widget settings where custom_svg is used (such as Premium Carousel, Premium Image Accordion, or similar widgets)Affected if custom_svg meta values exist in the database containing unsanitized content
-
Inspect stored custom_svg values for XSS payloadsExamine the raw values stored in wp_postmeta for the custom_svg meta_key using SQL: SELECT * FROM wp_postmeta WHERE meta_key = 'custom_svg'Affected if the stored values contain HTML tags, script elements, or event handler attributes (such as onload, onerror, onclick)
A user is affected if Premium Addons for Elementor version 4.11.70 or lower is installed AND the custom_svg parameter is being used with unsanitized input containing HTML or script content.
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 the Premium Addons for Elementor plugin to a version newer than 4.11.70 that properly sanitizes input and escapes output for the custom_svg parameter.
- Consultation2.0 h
- Implementation1.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4790 — 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-4790 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