dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-8756

MEDIUM · 5.3 CVSS v3.1 Published 2024-11-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 Quform - WordPress Form Builder plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.20.0 via the 'saveUploadedFile' function. This makes it possible for unauthenticated attackers to extract sensitive data, such as Personally Identifiable Information, from files uploaded by users. Files uploaded via forms created before version 2.21.0 will remain vulnerable to exposure after upgrading. To fully patch the plugin, site administrators should download any previously uploaded files, delete previously existing files and forms, and create the forms again after upgrading to version 2.21.0.

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 Quform WordPress Form Builder plugin versions up to 2.20.0 contain a vulnerability in the 'saveUploadedFile' function that allows unauthenticated attackers to access sensitive files uploaded through forms, potentially exposing PII and other confidential data.

MitigationUpgrade to version 2.21.0 immediately, then download all previously uploaded files, delete existing files and forms, and recreate the forms to fully remediate the exposure of historical uploads.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Verify Quform plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Quform - WordPress Form Builder', or check the /wp-content/plugins/iphorm-directory exists
    Affected if The Quform plugin is present in the WordPress installation
  2. Check installed Quform version
    In WordPress admin > Plugins > Installed Plugins > Quform, view the version number displayed, or read the version in the plugin's main PHP file header
    Affected if The version is 2.20.0 or lower (versions up to 2.20.0 are affected)
  3. Identify forms with file upload fields
    In Wordform admin panel, review all created forms and note which ones contain file upload fields. Check form settings for any uploaded file storage configuration
    Affected if Any form has file upload fields enabled, as these files are potentially accessible via the vulnerable saveUploadedFile function
  4. Check upload directory structure
    Examine the wp-content/uploads/iphorm directory (or custom upload path configured in Quform) for any uploaded files. List files and check if directory listing is enabled
    Affected if Uploaded files exist in Quform upload directories and are readable without authentication

User is affected if Quform plugin version 2.20.0 or lower is installed AND any forms contain file upload fields, as the saveUploadedFile function can be accessed unauthenticated to retrieve sensitive uploaded files.

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

Upgrade to version 2.21.0 immediately, then download all previously uploaded files, delete existing files and forms, and recreate the forms to fully remediate the exposure of historical uploads.

Recommended fix High confidence

Quform plugin version 2.21.0

  1. Create a complete backup of your WordPress site, including the database and all uploaded files
  2. Update the Quform plugin to version 2.21.0 or later through the WordPress admin dashboard or via WP-CLI
  3. Download all previously uploaded files from the server for archival and audit purposes (these files may contain exposed PII)
  4. Delete all previously uploaded files from the server that were submitted via Quform forms
  5. Delete all existing Quform forms from the WordPress admin panel
  6. Recreate all the deleted forms from scratch using the updated plugin (version 2.21.0+)
  7. Test the new forms to confirm they work correctly and that file uploads are now properly secured
  8. Verify that the plugin version shows 2.21.0 or later in the plugins list
Caveat The migration is required: all existing forms and previously uploaded files must be deleted and recreated after upgrading, as files uploaded before the fix remain exposed even after updating the plugin

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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