dbcve.org
Athemes Addons For ElementorWordPress extension · Athemes

CVE-2025-22646

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-27
Fix available
A fix is available. Upgrade to 1.0.9 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Syed Balkhi aThemes Addons for Elementor athemes-addons-for-elementor-lite allows Stored XSS.This issue affects aThemes Addons for Elementor: from n/a through <= 1.0.8.

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 confidence

A stored Cross-site Scripting (XSS) vulnerability exists in the aThemes Addons for Elementor WordPress plugin (versions up to 1.0.8). The vulnerability allows authenticated attackers with low-level privileges to inject malicious JavaScript code through plugin settings or Elementor elements, which is then stored in the database and executed when other users view affected pages.

MitigationUpdate the aThemes Addons for Elementor plugin to a version beyond 1.0.8 when a patch becomes available. As a temporary measure, implement proper input sanitization and output encoding on all user-supplied data rendered by the plugin.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Athemes Addons For ElementorWordPress extension
Affected:< 1.0.9

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'aThemes Addons for Elementor' or check the plugins directory for /wp-content/plugins/athemes-addons-for-elementor/
    Affected if The plugin is installed and active
  2. Check the installed version
    In WordPress admin Plugins page, click on the plugin name to view details, or check the plugin header in /wp-content/plugins/athemes-addons-for-elementor/athemes-addons-for-elementor.php for the Version field
    Affected if The version is 1.0.8 or lower (any version below 1.0.9)
  3. Identify users with low-level privileges
    Go to Users > All Users in WordPress admin and review user roles. Look for roles like Subscriber, Contributor, or any custom role with limited permissions
    Affected if Any user with Subscriber, Contributor, or low-level access exists on the site
  4. Inspect plugin settings for injected scripts
    Check WordPress options tables (wp_options) for suspicious script tags in any athemes_addons or similar plugin-related option names. Use SQL: SELECT * FROM wp_options WHERE option_name LIKE '%athemes%'
    Affected if Option values contain unencoded <script> tags, javascript: URLs, or onload/onerror event handlers

The environment is affected if the aThemes Addons for Elementor plugin is installed with version 1.0.8 or lower and low-privilege users exist who could have injected malicious scripts into plugin settings.

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
Upgrade available Upgrade to 1.0.9 or later
Fixed in 1.0.9
Interim mitigation

Update the aThemes Addons for Elementor plugin to a version beyond 1.0.8 when a patch becomes available. As a temporary measure, implement proper input sanitization and output encoding on all user-supplied data rendered by the plugin.

Recommended fix High confidence

Athemes Addons For Elementor version 1.0.9 or later

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Locate 'Athemes Addons for Elementor' in the plugin list
  4. Click 'Update now' if an update is available, or manually update by uploading version 1.0.9 or later from the WordPress plugin repository
  5. Verify the plugin updated successfully by checking the version number

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

Fix this in Athemes Addons For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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