dbcve.org
Qi Addons For ElementorWordPress extension · Qodeinteractive

CVE-2023-47680

MEDIUM · 5.4 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to after 1.6.3 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
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Qode Interactive Qi Addons For Elementor plugin <= 1.6.3 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 · high confidence

A stored Cross-Site Scripting (XSS) vulnerability in Qi Addons For Elementor plugin versions up to 1.6.3 allows authenticated users with contributor-level permissions or higher to inject malicious JavaScript that persists and executes when other users view the affected content.

MitigationUpdate Qi Addons For Elementor to a version newer than 1.6.3; if immediate update is not feasible, restrict or audit contributor-level user accounts.

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
Qi Addons For ElementorWordPress extension
Affected:<= 1.6.3

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. Identify the installed plugin version
    In WordPress admin, go to Plugins > Qi Addons For Elementor and read the version number from the plugin description, or check the plugin's main PHP file for the Version header comment
    Affected if The installed version is 1.6.3 or lower
  2. Count contributor-level user accounts
    Navigate to Users > All Users in WordPress admin and filter or count users with the Contributor role
    Affected if There are one or more contributor-level user accounts active on the site
  3. Inspect content authored by contributors
    Go to Posts > All Posts and filter by Author to review content created by contributor-level users; examine the HTML source for any script tags, event handlers (onload, onerror, onclick), or suspicious URL patterns
    Affected if Any content authored by contributors contains unexpected script tags, javascript: URLs, or XSS vectors like <img onerror= or similar
  4. Review widget and page builder content
    If using Elementor, edit recent pages and check any Qi Addons widgets for manually injected JavaScript or event handlers in text fields, button links, or custom HTML areas
    Affected if Qi Addons widgets contain raw script tags or suspicious JavaScript in normally plain-text fields
  5. Check for recent unauthorized content changes
    Review the WP revisions or audit log for recent posts/pages edited by contributor-level users, looking for sudden additions of script tags or HTML containing JavaScript
    Affected if Recent revisions show injection of script tags or JavaScript-containing HTML that was not part of the original content

You are affected if the plugin version is 1.6.3 or lower AND at least one contributor-level user account exists and has authored content containing injected JavaScript or script tags.

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 a release after 1.6.3
Interim mitigation

Update Qi Addons For Elementor to a version newer than 1.6.3; if immediate update is not feasible, restrict or audit contributor-level user accounts.

Recommended fix High confidence

1.6.4 or later (any version higher than 1.6.3)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Qi Addons For Elementor' in the plugin list
  4. Check if an update is available and update to the latest version
  5. Verify the update was applied successfully

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

Fix this in Qi Addons For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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