dbcve.org
Qode Essential AddonsWordPress extension · Qodeinteractive

CVE-2024-50457

HIGH · 8.8 CVSS v3.1 Published 2024-10-28
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 Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Qode Qode Essential Addons qode-essential-addons.This issue affects Qode Essential Addons: 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

This is a Remote File Inclusion (RFI) vulnerability in Qode Essential Addons, a WordPress plugin. The flaw allows attackers to include remote files via improper input validation in PHP include/require statements, potentially enabling arbitrary code execution on the server.

MitigationUpdate Qode Essential Addons to the latest version if a patch is available. If no patch exists, disable the plugin immediately and implement WAF rules to block suspicious file inclusion parameters.

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
Qode Essential AddonsWordPress 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. Verify plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Qode Essential Addons' by Qodeinteractive. Alternatively, check the /wp-content/plugins/ directory for a folder named 'qode-essential-addons'.
    Affected if The plugin is installed and active on the WordPress site.
  2. Determine installed version
    In WordPress admin, find the plugin in the plugins list and note the version number displayed beneath the plugin name. Or check the main plugin file (usually qode-essential-addons.php) for the 'Version' header in the plugin comments.
    Affected if The version number is lower than 1.6.4.
  3. Compare version to affected range
    Review the version found in step 2. The vulnerability affects versions strictly below 1.6.4.
    Affected if Installed version is < 1.6.4.
  4. Inspect server access logs for RFI indicators
    Review web server access logs (Apache, Nginx) for requests to the plugin endpoints containing http://, https://, or ../ in query parameters that may indicate RFI exploitation attempts.
    Affected if Suspicious requests with remote file references are found in logs targeting the plugin.

The site is affected if Qode Essential Addons is installed with a version number lower than 1.6.4.

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 Qode Essential Addons to the latest version if a patch is available. If no patch exists, disable the plugin immediately and implement WAF rules to block suspicious file inclusion parameters.

Recommended fix High confidence

1.6.4

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. Find 'Qode Essential Addons' 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 is showing 1.6.4 after update
  6. Test that your site functions normally after the update

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

Fix this in Qode Essential Addons Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
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,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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