dbcve.org
Qi BlocksWordPress extension · Qodeinteractive

CVE-2024-49690

HIGH · 8.8 CVSS v3.1 Published 2024-10-23
Fix available
A fix is available. Upgrade to 1.3.3 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 Qi Blocks qi-blocks.This issue affects Qi Blocks: from n/a through <= 1.3.2.

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 Remote File Inclusion (RFI) vulnerability in Qode Qi Blocks plugin versions up to 1.3.2 allows unauthenticated attackers to include remote files via improper input validation in PHP include/require statements, potentially leading to Remote Code Execution on the server.

MitigationUpdate Qi Blocks to the latest patched version; as an interim measure, disable 'allow_url_include' in PHP configuration and implement input validation/waf to block malicious file inclusion attempts.

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 BlocksWordPress extension
Affected:< 1.3.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
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 Qi Blocks plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Qi Blocks' by Qodeinteractive in the installed plugins list, or check the /wp-content/plugins/ directory for the qi-blocks folder
    Affected if The Qi Blocks plugin is present on the WordPress site
  2. Check installed Qi Blocks version
    In WordPress admin, go to Plugins > Installed Plugins > Qi Blocks and view the version number, or check the main plugin file (typically qi-blocks.php) for the 'Version' header comment
    Affected if The version number is lower than 1.3.3 (e.g., 1.3.2, 1.3.1, 1.0.x, etc.)
  3. Identify vulnerable file inclusion parameters
    Review plugin PHP files in the qi-blocks/includes/ directory, specifically looking for include(), include_once(), require(), or require_once() calls that use dynamic variables or parameters (e.g., include($_GET['file']) or include($some_variable))
    Affected if The plugin code contains dynamic file inclusion functions using user-supplied input without proper validation
  4. Check if file inclusion endpoints are accessible
    Test common RFI entry points by attempting to include a non-malicious local file (e.g., ?file=../index.php) via GET parameters that the plugin handles, if such parameters are discoverable in the plugin code
    Affected if The vulnerable parameters are exposed and accept arbitrary file paths or URLs
  5. Review server access logs for suspicious inclusion requests
    Examine Apache/nginx access logs in /var/log/ for patterns like 'GET /?file=http://' or 'GET /?file=ftp://' or other remote URL patterns pointing to the qi-blocks plugin paths
    Affected if Logs show requests to include remote URLs or suspicious file paths through the Qi Blocks plugin

The environment is affected if Qi Blocks version is below 1.3.3 AND the plugin has accessible file inclusion functionality using unsanitized user input.

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.3.3 or later
Fixed in 1.3.3
Interim mitigation

Update Qi Blocks to the latest patched version; as an interim measure, disable 'allow_url_include' in PHP configuration and implement input validation/waf to block malicious file inclusion attempts.

Recommended fix Moderate confidence

Qi Blocks version 1.3.3

  1. Update Qi Blocks plugin to version 1.3.3 or later via WordPress admin dashboard (Plugins > Updates)
  2. Alternatively, download the latest version from WordPress plugin repository or the official Qode website
  3. After updating, verify the plugin is running version 1.3.3 or higher in Plugins > Installed Plugins
  4. Test critical site functionality to ensure the update does not break existing features

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

Fix this in Qi Blocks 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-2024-49690 — 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-49690 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