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

CVE-2026-11390

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-14
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 5 weeks old

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 News Kit Addons For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Site Logo Title and Single Author Box Widgets in all versions up to, and including, 1.4.6 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. Exploitation requires an attacker to intercept and modify the elementor_ajax AJAX save request in order to bypass the client-side SELECT control restrictions and submit arbitrary tag-name values.

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 News Kit Addons For Elementor plugin versions up to 1.4.6 suffer from stored XSS in the Site Logo Title and Single Author Box widgets due to missing input sanitization and output escaping. Authenticated contributors can bypass client-side SELECT restrictions by intercepting elementor_ajax save requests and injecting arbitrary tag names, causing scripts to execute on page access.

MitigationUpdate to version 1.4.7 or later; review and sanitize existing widget content; consider using a WAF rule to block malicious AJAX requests targeting elementor_ajax.

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. Verify plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'News Kit Addons For Elementor' in the list. Note its current version displayed next to the plugin name.
    Affected if The plugin is installed and the version listed is 1.4.6 or lower.
  2. Confirm exact version number
    Click on the plugin name in the plugins list to view details, or check the plugin files in wp-content/plugins/news-kit-addons-for-elementor/ for a version definition file.
    Affected if Version is 1.4.6 or any version below 1.4.7.
  3. Identify active Site Logo Title widgets
    In Elementor editor, search for 'Site Logo Title' widget in the widget panel. Check pages/posts where this widget has been added. Review the widget settings for any custom title text fields.
    Affected if The Site Logo Title widget is in use on any page and the site runs a vulnerable plugin version.
  4. Identify active Single Author Box widgets
    In Elementor editor, search for 'Single Author Box' widget. Check content where this widget has been added. Review the widget settings for author name, bio, or other text input fields.
    Affected if The Single Author Box widget is in use on any page and the site runs a vulnerable plugin version.
  5. Inspect widget content for malicious payloads
    For pages using these widgets, view the page source or use browser developer tools to inspect the rendered HTML. Look for unexpected <script> tags, javascript: URLs, or event handlers (onclick, onerror, onload) in title or author fields.
    Affected if Any script tags or javascript event handlers are present in the rendered output of these widgets that were not intentionally added by an administrator.

The environment is affected if News Kit Addons For Elementor version 1.4.6 or lower is installed AND the Site Logo Title or Single Author Box widgets are in use on the site.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 1.4.7 or later; review and sanitize existing widget content; consider using a WAF rule to block malicious AJAX requests targeting elementor_ajax.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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