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

CVE-2026-8613

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-10
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 aThemes Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'title_tag' Widget Setting in all versions up to, and including, 1.1.8 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. This affects the Posts Timeline widget as well as the Posts Carousel widget across its default, Banner, and Modern skins, all of which omit the whitelist validation that is correctly applied in the Posts List 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 aThemes Addons for Elementor plugin versions up to 1.1.8 contains a stored XSS vulnerability in the Posts Timeline and Posts Carousel widgets (across default, Banner, and Modern skins) where the 'title_tag' parameter lacks proper input sanitization and output escaping. Authenticated users with contributor-level permissions can inject arbitrary JavaScript via this parameter.

MitigationUpdate to version 1.1.9 or later, which implements the whitelist validation pattern already present in the Posts List widget for the affected widgets and skins.

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 aThemes Addons for Elementor is installed
    Go to WordPress Dashboard > Plugins and locate 'aThemes Addons for Elementor' or check the plugin files for version information in the main plugin header
    Affected if The plugin is installed and the version is lower than 1.1.9
  2. Identify use of Posts Timeline widget
    Search WordPress pages, posts, or Elementor templates for the Posts Timeline widget usage, or query the wp_postmeta table for meta_value containing 'posts-timeline'
    Affected if The Posts Timeline widget is present in any published content
  3. Identify use of Posts Carousel widget
    Search WordPress pages, posts, or Elementor templates for the Posts Carousel widget usage, or query the wp_postmeta table for meta_value containing 'posts-carousel'
    Affected if The Posts Carousel widget is present in any published content
  4. Check title_tag setting in affected widgets
    Examine the widget settings in Elementor editor or inspect the stored meta data for the title_tag parameter in the relevant widget instances
    Affected if The title_tag parameter exists in the widget configuration and the site allows contributor-level users to edit these widgets

The environment is affected if aThemes Addons for Elementor version is below 1.1.9 AND either the Posts Timeline or Posts Carousel widgets are in use on the site, allowing authenticated contributors to modify the title_tag parameter.

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 to version 1.1.9 or later, which implements the whitelist validation pattern already present in the Posts List widget for the affected widgets and skins.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (greater than 1.1.8)

  1. 1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  2. 2. Locate the 'aThemes Addons for Elementor' plugin
  3. 3. Check the current installed version (should be 1.1.8 or below)
  4. 4. Update the plugin to the latest available version from the WordPress plugin repository
  5. 5. After updating, verify the 'title_tag' setting in the Posts Timeline and Posts Carousel widgets now properly sanitizes input

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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