Skip to main content

News Kit Addons EUVDEUVD-2026-115664

| CVE-2026-120524 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-11-03 Wordfence GHSA-w8r5-69q2-3m5g
6.4
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Register/authenticate as subscriber
  2. Delivery
    Submit formData with \u003c-encoded payload
  3. Exploit
    Bypass sanitize_text_field before json_decode
  4. Execution
    Overwrite _elementor_data on target post
  5. Impact
    Stored script executes on page view

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an authenticated account with subscriber-level access or above - exploitable in practice mainly on sites permitting self-registration. Two specific product conditions enable it: (1) an operator-precedence bug in handle_scripts() causes the admin bundle and its inlined nekit-admin-nonce to be enqueued on every admin screen reachable by subscribers (e.g. /wp-admin/profile.php), handing low-privileged users the nonce needed for the request; and (2) sanitize_text_field() is applied to the raw JSON string before json_decode(), so angle brackets encoded as \u003c/\u003e survive sanitization and are restored to literal '<'/'>', permitting overwrite of _elementor_data on any post. Limiting factors: authentication is mandatory (not unauthenticated), the plugin (News Kit Addons For Elementor, versions ≤1.4.8) must be installed and active, and realistic impact depends on another user - typically an admin or visitor - later viewing the injected page for the stored script to fire.

Impact

This is a genuine but mid-tier priority. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N, base 6.4) indicates a network-reachable, low-complexity stored XSS requiring only subscriber-level authentication (PR:L) with no victim interaction to inject, and a changed scope (S:C) reflecting that injected script executes in the browser context of any user who later views the poisoned page. The vuln.today Decision label is 'this_month' - a scheduled-remediation signal, not act_now or emergency. It is NOT in CISA KEV and no EPSS score was supplied, so there is no evidence of active or widespread exploitation; the references are Wordfence's analysis and WordPress trac source lines documenting the flaw, not a verified weaponized exploit. The low privilege barrier is meaningful on sites that allow open registration (common for WooCommerce/membership sites), where any subscriber becomes an attacker - this is the main factor that elevates it above a trivial issue. Impact is capped at C:L/I:L (no availability impact), consistent with script injection rather than full compromise. Missing data to note explicitly: no EPSS, no KEV, and no vendor-confirmed fixed version in the provided input (only a trac changeset reference suggesting a patch exists).

Exploit ScenarioDerived

On a WordPress site with open user registration, an attacker registers a subscriber account and submits a request to the plugin's handler with a crafted 'formData' parameter whose angle brackets are encoded as \u003c/\u003e so they survive sanitize_text_field() before json_decode(), overwriting _elementor_data on a target post with a malicious script. When an administrator or other visitor subsequently opens that page, the script executes in their browser. No public, verified working exploit code was identified at time of analysis, though Wordfence has published a technical write-up pinpointing the vulnerable code paths.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Nov 03, 2026

Stored cross-site scripting in the News Kit Addons For Elementor WordPress plugin (all versions up to and including 1.4.8) lets an authenticated attacker with subscriber-level access or above plant arbitrary script inside a post's Elementor data, which executes for any user - typically an administrator or site visitor - who later opens the injected page. This is a genuine but mid-tier priority: the CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N, 6.4) is not unauthenticated, so practical exposure is concentrated on sites that permit self-registration or otherwise hand out low-privileged accounts, and the stored payload only fires when a second party views the affected page. No public exploit identified at time of analysis, and the issue is not in CISA KEV; the decision label from the priority feed is this_month.

RemediationAI

Upstream fix available (changeset 3749965 in the WordPress plugin repository, https://plugins.trac.wordpress.org/changeset?reponame=&old=3749965%40news-kit-elementor-addons&new=3749965%40news-kit-elementor-addons); a released patched version number is not independently confirmed in the available data, so update the plugin through the WordPress admin to the newest published release and verify the installed version is above 1.4.8. Where an update cannot be applied immediately, the highest-value compensating control is to close the authentication prerequisite: disable public/self-service user registration and audit existing Subscriber accounts, since without a low-privileged foothold the flaw is unreachable - the trade-off is loss of open registration and manual account review overhead. Restricting or blocking access to /wp-admin/profile.php and other subscriber-reachable admin screens (for example via a WAF or an admin-side access rule) removes the nonce-leak step but can break legitimate profile editing for low-privileged users. A WAF rule denying requests that carry \u003c/\u003e sequences in the formData parameter, or that POST Elementor data from Subscriber-level sessions, reduces exploitation attempts with the usual risk of false positives on legitimate encoded content. Deactivating the plugin entirely removes the exposure at the cost of the site's News Kit Elementor widgets. Reviewing _elementor_data post meta for unexpected script markup on existing posts is advisable to detect prior injections. The vendor advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/7793c171-8aca-461c-9942-9f4d075be5ae?source=cve should be tracked for the fixed release.

Affected VersionsENISA

News Kit Addons For Elementor 0 ≤1.4.8

Affected Packages

euvd news_kit_addons_for_elementor no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The plugin (WordPress.org slug news-kit-elementor-addons, vendor blazethemes, CPE cpe:2.3:a:blazethemes:news_kit_addons_for_elementor) is an Elementor add-on pack written in PHP, and the flaw is a classic CWE-79 improper neutralization of input during web page generation, made reachable by two implementation mistakes. First, an operator-precedence bug in handle_scripts() causes the plugin's admin JavaScript bundle - and the nekit-admin-nonce inlined into it - to be enqueued on every admin screen a Subscriber can reach, such as /wp-admin/profile.php, so a low-privileged user is handed the nonce that should gate the privileged request. Second, the 'formData' parameter is passed through sanitize_text_field() as a raw JSON string before json_decode() is called; Unicode-escaped angle brackets (\u003c and \u003e) survive sanitization as harmless-looking text and are then restored to literal '<' and '>' after decoding, defeating the escaping. The decoded structure is written into the _elementor_data post meta, which Elementor later renders as page content, converting the injected markup into persistent script execution on any post. The trigger path and the two enabling conditions are documented in the upstream source at admin/admin.php (lines ~732, ~748, ~1578, ~1582 in tag 1.4.7); the trigger is not further described beyond these code references.

Know when News Kit Addons For Elementor gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY 6.4 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
vuln.today AI 6.4 MEDIUM

Network-reachable with low complexity; PR:L because subscriber authentication is required; S:C and C:L/I:L reflect script execution in a victim's browser context; A:N as availability is unaffected.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

The News Kit Addons For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'formData' parameter in all versions up to, and including, 1.4.8 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is possible because an operator-precedence bug in handle_scripts() causes the admin bundle - and its inlined nekit-admin-nonce - to be enqueued on every admin screen accessible to Subscribers (such as /wp-admin/profile.php), and because sanitize_text_field() is applied to the raw JSON string before json_decode(), allowing angle brackets encoded as \u003c/\u003e to survive sanitization and be restored to literal angle brackets, enabling overwrite of _elementor_data on any post.

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Prevalence
Low
niche third-party Elementor addon, limited install base
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy