dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-6314

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The IQ Testimonials plugin for WordPress is vulnerable to arbitrary file uploads due to insufficient file type validation in the 'process_image_upload' function in versions up to, and including, 2.2.7. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. This can only be exploited if the 'gd' php extension is not loaded on the server.

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

The IQ Testimonials WordPress plugin (versions up to 2.2.7) has an arbitrary file upload vulnerability in the process_image_upload function due to insufficient file type validation. Unauthenticated attackers can upload arbitrary files to the server, potentially achieving remote code execution. The vulnerability is exploitable only when the gd PHP extension is not loaded.

MitigationUpdate the plugin to a patched version once available. As a compensating control, ensure the gd PHP extension is loaded (this blocks exploitation but does not fix the underlying validation flaw). Consider disabling the plugin until patched if gd cannot be ensured.

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

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm IQ Testimonials plugin is installed
    Locate the plugin files in the WordPress wp-content/plugins directory, looking for a folder named 'iq-testimonials' or similar. Check for the existence of the main plugin PHP file.
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Identify the installed plugin version
    Open the plugin's main PHP file or readme.txt and locate the Version header. Compare this version number to the affected range (versions up to and including 2.2.7).
    Affected if The installed version is 2.2.7 or lower
  3. Verify gd PHP extension status
    Run 'php -m' from command line or use phpinfo() to list loaded PHP modules. Search for 'gd' in the output.
    Affected if The gd extension does NOT appear in the list of loaded PHP modules
  4. Confirm upload functionality is accessible
    Check the WordPress site's wp-admin or public-facing areas where image upload functionality exists for the plugin. Alternatively, inspect plugin source code for the process_image_upload function.
    Affected if The upload endpoint exists and is accessible without authentication

The environment is affected only if the IQ Testimonials plugin is installed at version 2.2.7 or lower AND the gd PHP extension is not loaded, allowing unauthenticated file uploads to succeed.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a patched version once available. As a compensating control, ensure the gd PHP extension is loaded (this blocks exploitation but does not fix the underlying validation flaw). Consider disabling the plugin until patched if gd cannot be ensured.

Recommended fix High confidence

Latest version of IQ Testimonials plugin (version 2.2.8 or higher)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate IQ Testimonials in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/iq-testimonials and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the new version number reflects the update

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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