Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-8756: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in ThemeCatcher Quform - WordPress Form Builder

0
Medium
VulnerabilityCVE-2024-8756cvecve-2024-8756cwe-200
Published: Sat Nov 09 2024 (11/09/2024, 05:40:23 UTC)
Source: CVE Database V5
Vendor/Project: ThemeCatcher
Product: Quform - WordPress Form Builder

Description

CVE-2024-8756 is a medium severity vulnerability in the Quform WordPress Form Builder plugin (up to version 2. 20. 0) that allows unauthenticated attackers to access sensitive information from files uploaded via forms. The vulnerability arises from the 'saveUploadedFile' function, which improperly exposes Personally Identifiable Information (PII) contained in uploaded files. Notably, files uploaded before upgrading to version 2. 21. 0 remain vulnerable even after patching, requiring administrators to manually download and delete old files and recreate forms. Exploitation requires no authentication or user interaction and can lead to unauthorized data disclosure. There are no known exploits in the wild currently. Organizations using this plugin should promptly upgrade to version 2.

AI-Powered Analysis

AILast updated: 02/25/2026, 22:41:42 UTC

Technical Analysis

CVE-2024-8756 is a vulnerability classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) affecting the Quform WordPress Form Builder plugin developed by ThemeCatcher. The issue exists in all versions up to and including 2.20.0 within the 'saveUploadedFile' function, which handles files uploaded through forms. Due to improper access controls or insufficient validation, unauthenticated attackers can retrieve sensitive data such as Personally Identifiable Information (PII) from these uploaded files. The vulnerability is particularly insidious because it does not require any authentication or user interaction, making it accessible remotely over the network. Furthermore, even after upgrading to the patched version 2.21.0, files uploaded via forms created before the upgrade remain exposed, as the vulnerability affects stored files rather than just the plugin code. To fully remediate, administrators must download and securely delete all previously uploaded files and recreate forms post-upgrade. The CVSS v3.1 base score is 5.3 (medium), reflecting the ease of exploitation (network, no privileges, no user interaction) but limited impact (confidentiality loss only, no integrity or availability impact). No known exploits have been reported in the wild, but the widespread use of WordPress and this popular form plugin increases the potential attack surface.

Potential Impact

The primary impact of this vulnerability is unauthorized disclosure of sensitive information, including Personally Identifiable Information (PII), which can lead to privacy violations, regulatory non-compliance (e.g., GDPR, CCPA), and reputational damage for affected organizations. Attackers can extract uploaded files without authentication, potentially harvesting user-submitted data such as contact details, identification documents, or other confidential information. Although the vulnerability does not affect data integrity or availability, the exposure of sensitive data can facilitate further attacks such as identity theft, phishing, or social engineering. Organizations using the affected plugin versions are at risk, especially those handling sensitive user data through forms. The persistence of vulnerable files after patching increases the risk window and complicates remediation efforts. Given WordPress's global popularity and the plugin's usage, a large number of websites could be affected, including e-commerce, healthcare, education, and government sectors.

Mitigation Recommendations

To mitigate CVE-2024-8756, site administrators should immediately upgrade the Quform plugin to version 2.21.0 or later, which contains the fix for the 'saveUploadedFile' function vulnerability. However, upgrading alone is insufficient because files uploaded via forms created before the upgrade remain exposed. Therefore, administrators must: 1) Identify and download all previously uploaded files stored by the plugin to secure offline storage; 2) Delete all previously existing uploaded files and associated forms from the WordPress installation to remove vulnerable data; 3) Recreate the forms anew after upgrading to ensure that new uploads are handled securely; 4) Review access permissions on upload directories to restrict unauthorized access; 5) Monitor web server logs for suspicious access attempts to uploaded files; 6) Consider implementing additional web application firewall (WAF) rules to block unauthorized file access; 7) Educate site users and administrators about the risk and remediation steps. Regular backups and security audits should be conducted to ensure no residual exposure remains.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2024-09-12T16:15:17.805Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6b30b7ef31ef0b54f24d

Added to database: 2/25/2026, 9:35:44 PM

Last enriched: 2/25/2026, 10:41:42 PM

Last updated: 2/26/2026, 9:43:21 AM

Views: 1

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats