dbcve.org
Generate Pdf Using Contact Form 7WordPress extension · Zealousweb

CVE-2024-6317

HIGH · 8.8 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to 4.1.3 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Generate PDF using Contact Form 7 plugin for WordPress is vulnerable to Cross-Site Request Forgery to Arbitrary File Upload in versions up to, and including, 4.1.2. This is due to missing nonce validation and the plugin not properly validating a file or its path prior to deleting it in the 'wp_cf7_pdf_dashboard_html_page' function. This makes it possible for unauthenticated attackers to delete arbitrary files, including the wp-config.php file, which can make site takeover and remote code execution possible via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 Generate PDF using Contact Form 7 WordPress plugin is vulnerable to CSRF leading to arbitrary file deletion in versions up to 4.1.2. The wp_cf7_pdf_dashboard_html_page function lacks nonce validation and proper file/path validation, allowing unauthenticated attackers to delete any file on the server including wp-config.php by tricking an authenticated administrator into clicking a malicious link.

MitigationUpdate the plugin to the latest version immediately. Additionally, implement anti-CSRF tokens (nonces) for admin actions and validate file paths to prevent directory traversal attacks.

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
Generate Pdf Using Contact Form 7WordPress extension
Affected:< 4.1.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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 the plugin is installed
    Check if the Generate PDF using Contact Form 7 plugin exists in your WordPress installation at wp-content/plugins/ or via the WordPress admin plugin list.
    Affected if The plugin is present in the installation regardless of version.
  2. Identify the installed version
    Locate the plugin version number in the plugin header comment within the main PHP file (usually wp-content/plugins/generate-pdf-using-contact-form-7/*.php) or in the readme.txt file in the plugin directory.
    Affected if The installed version is below 4.1.3 (such as 4.1.2, 4.1.1, etc.).
  3. Confirm the plugin is active
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Verify the Generate PDF using Contact Form 7 plugin shows as 'Active'.
    Affected if The plugin is activated on the WordPress site.
  4. Check for the vulnerable function
    Examine the plugin source code for the wp_cf7_pdf_dashboard_html_page function. If present, verify whether it processes file deletion requests without nonce validation and without sanitizing file paths for directory traversal.
    Affected if The vulnerable function exists and processes file deletion parameters without proper validation.

You are affected if the plugin is installed and active with a version lower than 4.1.3, and the vulnerable dashboard file deletion function is present and accessible.

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 4.1.3 or later
Fixed in 4.1.3
Interim mitigation

Update the plugin to the latest version immediately. Additionally, implement anti-CSRF tokens (nonces) for admin actions and validate file paths to prevent directory traversal attacks.

Recommended fix High confidence

4.1.3

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Generate PDF using Contact Form 7' in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to version 4.1.3 or higher
  5. Alternatively, navigate to Dashboard > Updates and select the plugin to update
  6. Verify the updated version is 4.1.3 or later after the update completes

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

Fix this in Generate Pdf Using Contact Form 7 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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