dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-3870

MEDIUM · 5.3 CVSS v3.1 Published 2024-05-02
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 Contact Form 7 Database Addon – CFDB7 plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 1.2.6.8 via the cfdb7_before_send_mail function. This can allow unauthenticated attackers to extract sensitive data, such as Personally Identifiable Information, from files uploaded by users.

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

The CFDB7 WordPress plugin has a sensitive information exposure vulnerability in the cfdb7_before_send_mail function. This function, intended to handle form submissions, improperly exposes uploaded files containing user data (including PII) to unauthenticated attackers. The vulnerability allows remote, unauthenticated users to directly access files submitted through contact forms without any authentication or authorization checks.

MitigationUpdate the CFDB7 plugin to the latest version immediately. Additionally, review and restrict access to any publicly accessible file upload directories, and ensure the cfdb7_before_send_mail function enforces proper authentication and authorization checks before serving any file content.

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 CFDB7 plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'CFDB7' (Contact Form 7 Database). Note the installed version number.
    Affected if CFDB7 plugin is installed and active
  2. Compare installed version to patched release
    Check the WordPress plugin repository or your plugin changelog for the version that addresses CVE-2024-3870. Compare your installed version against it.
    Affected if Installed version is older than the patched version (the vulnerability allows unauthenticated file access)
  3. Identify if file upload forms exist
    In WordPress admin, check your CFDB7 settings and any Contact Form 7 forms that include file upload fields (type=file). Look for forms that collect user-submitted files.
    Affected if Active forms with file upload fields are in use and storing submissions in CFDB7
  4. Check upload directory is publicly accessible
    Locate the CFDB7 upload directory (typically wp-content/uploads/cfdb7_or similar path). Attempt to access a known submission file directly via browser URL without logging in, or check file permissions (should not be world-readable).
    Affected if Upload directory contents are accessible via direct URL without authentication
  5. Test unauthenticated access to cfdb7_before_send_mail
    Send a direct HTTP request to the cfdb7_before_send_mail endpoint (typically via wp-admin/admin-ajax.php?action=cfdb7_file or similar) without providing any authentication credentials.
    Affected if The endpoint returns file contents or submission data without requiring login

If CFDB7 is installed with file upload forms and the upload directory or cfdb7_before_send_mail endpoint is accessible without authentication, the environment is affected by CVE-2024-3870.

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 CFDB7 plugin to the latest version immediately. Additionally, review and restrict access to any publicly accessible file upload directories, and ensure the cfdb7_before_send_mail function enforces proper authentication and authorization checks before serving any file content.

Recommended fix Moderate confidence

1.2.6.9 or later (latest stable release)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Contact Form 7 Database Addon – CFDB7'
  4. Check the current version installed
  5. If version is 1.2.6.8 or lower, click 'Update Now' to upgrade to the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/contact-form-cfdb7/ and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the new version number in the plugins list

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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