CVE-2026-48870
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 · uneditedSubscriber Cross Site Scripting (XSS) in King Addons for Elementor <= 51.1.62 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 confidenceA stored Cross Site Scripting (XSS) vulnerability exists in King Addons for Elementor plugin versions 51.1.62 and below, allowing authenticated users with subscriber-level privileges to inject malicious JavaScript code through plugin features.
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.
-
Verify King Addons for Elementor versionNavigate to WordPress admin > Plugins > King Addons for Elementor and check the installed version number displayed under the plugin name, or use WP-CLI: wp plugin list --name='king-addons-for-elementor' --format=tableAffected if The installed version is 51.1.62 or any version number lower than 51.1.62
-
Confirm subscriber-level user accounts existGo to WordPress admin > Users and review the user list, or use WP-CLI: wp user list --role=subscriber --format=countAffected if There is at least one user account with the subscriber role; the vulnerability is exploitable by any subscriber-level user
-
Inspect plugin feature settings for user input fieldsReview King Addons settings under Elementor > King Addons and identify any features that accept and store user-submitted content (such as custom widgets, form builders, or content display modules)Affected if Any feature that allows subscriber-level users to submit or edit content through the plugin is enabled and accessible to subscribers
-
Audit recent content submissions from low-privilege usersReview posts, pages, or custom post types created by users with subscriber role since the plugin was installed; inspect HTML source of stored content for suspicious script tagsAffected if Stored content authored by subscribers contains unsanitized JavaScript, iframe, or script injection payloads in title, content, or custom fields
-
Check server access logs for XSS proof-of-concept patternsSearch web server logs (Apache/Nginx) for requests containing common XSS payloads (such as <script>, javascript:, onerror=, onload=) submitted to plugin-related endpointsAffected if Logs show POST requests with XSS payloads submitted from authenticated users with subscriber role to plugin endpoints
Your environment is affected if King Addons for Elementor version 51.1.62 or below is installed AND subscriber-level user accounts have access to plugin features that accept and store user-submitted 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 King Addons for Elementor to the latest version immediately; if no update is available, consider disabling the plugin or implementing additional input sanitization as a temporary workaround.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48870 — 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-48870 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