dbcve.org
Qi Addons For ElementorWordPress extension · Qodeinteractive

CVE-2023-47679

HIGH · 8.8 CVSS v3.1 Published 2024-05-17
Fix available
A fix is available. Upgrade to 1.6.4 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in QODE Interactive Qi Addons For Elementor allows PHP Local File Inclusion.This issue affects Qi Addons For Elementor: from n/a through 1.6.3.

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 path traversal vulnerability in Qi Addons For Elementor plugin allows attackers to manipulate file path parameters to include arbitrary PHP files from the server, leading to local file inclusion. This occurs due to insufficient validation of path inputs before use in include/require statements.

MitigationUpdate Qi Addons For Elementor to the latest patched version. If no update is available, disable the plugin until a fix is released. Implement web application firewall rules to block path traversal patterns (../, etc.) as a temporary mitigation.

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.4

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Check if Qi Addons For Elementor plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Qi Addons For Elementor' in the list of installed plugins.
    Affected if The plugin appears in the installed plugins list and is activated.
  2. Determine the installed version of Qi Addons For Elementor
    In the WordPress admin, go to Plugins > Installed Plugins. Click on 'Qi Addons For Elementor' to view the plugin details, or look for the version number displayed next to the plugin name. Alternatively, check the plugin header in /wp-content/plugins/qi-addons-for-elementor/qi-addons-for-elementor.php for the 'Version' comment.
    Affected if The installed version is lower than 1.6.4 (for example, 1.6.3, 1.6.2, 1.5.0, etc.).
  3. Verify the plugin is actively processing file include requests
    Review your web server access logs for requests to the Qi Addons For Elementor plugin that include path parameters (look for URLs containing 'qi-addons-for-elementor' with 'require', 'include', or path-related query parameters). Check if the plugin's widgets or shortcodes that handle file paths are in use on the site.
    Affected if The plugin is active and accessible, and there are requests that could trigger file inclusion functionality.
  4. Identify if path traversal protection is missing
    Test a safe, benign path traversal attempt on an endpoint that uses file inclusion within the plugin (if such functionality exists). Observe whether the application allows climbing directory structures using '../' sequences in parameters.
    Affected if The plugin accepts and processes path parameters without sanitizing '../' sequences, allowing directory traversal.

The environment is affected if Qi Addons For Elementor plugin is installed with a version lower than 1.6.4 and the plugin exposes file inclusion functionality that lacks proper path validation.

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.6.4 or later
Fixed in 1.6.4
Interim mitigation

Update Qi Addons For Elementor to the latest patched version. If no update is available, disable the plugin until a fix is released. Implement web application firewall rules to block path traversal patterns (../, etc.) as a temporary mitigation.

Recommended fix Moderate confidence

1.6.4

  1. Backup your WordPress site and database before updating any plugins
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Find 'Qi Addons For Elementor' in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 1.6.4 of the plugin
  5. Verify the plugin version shows 1.6.4 after updating
  6. Test that Elementor page builder functionality works correctly with the updated plugin

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
  • 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-2023-47679 — 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-47679 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