CVE-2024-6316
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 · uneditedThe 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 missing file type validation in the 'wp_cf7_pdf_dashboard_html_page' function. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make 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. CVE-2024-37555 is a duplicate of this issue.
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 confidenceThe Generate PDF using Contact Form 7 WordPress plugin has a CSRF-to-Arbitrary File Upload vulnerability in the wp_cf7_pdf_dashboard_html_page function. The function lacks nonce validation (allowing forged requests) and file type validation (allowing any file extension), enabling unauthenticated attackers to upload malicious files via tricking an administrator into clicking a crafted link.
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< 4.1.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Generate Pdf Using Contact Form 7' by Zealousweb. Note the installed version number.Affected if The plugin is installed and the version shown is below 4.1.3 (e.g., 4.1.2, 4.1.1, etc.)
-
Verify plugin version via filesystemCheck the plugin main file (wp-content/plugins/generate-pdf-using-contact-form-7/generate-pdf-using-contact-form-7.php) for the Version header comment, or query the WordPress database plugins table for the plugin version.Affected if The version retrieved is less than 4.1.3
-
Check if admin dashboard upload feature existsAccess the plugin settings page in WordPress admin (typically under Contact > PDF Settings or a dedicated Generate PDF menu). Look for any file upload, import, or dashboard HTML functionality.Affected if The plugin admin interface with upload/import capabilities is accessible and the plugin version is below 4.1.3
-
Inspect plugin source for nonce validationExamine the plugin PHP files for the function 'wp_cf7_pdf_dashboard_html_page' and check if it includes nonce verification using wp_verify_nonce or check_admin_referer before processing requests.Affected if The function exists in the plugin code without nonce validation checks and the version is below 4.1.3
-
Inspect plugin source for file type validationReview the same function for file type or mime type validation (e.g., using wp_check_filetype, checking $_FILES type, or an allowlist).Affected if The function allows file uploads without proper file type/mime validation and the version is below 4.1.3
If the Zealousweb Generate Pdf Using Contact Form 7 plugin is installed with a version lower than 4.1.3, the vulnerable function lacks both nonce and file type validation, meaning the environment is affected by CVE-2024-6316.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.1.3
Update to the latest plugin version when available; otherwise implement nonce validation on the affected function, add strict file type/mime validation with allowlist, and verify file contents before allowing storage.
4.1.3
- Backup your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Locate 'Generate PDF using Contact Form 7' in the plugin list
- Click 'Update now' if an update is available, or manually update to version 4.1.3 or later
- Verify the plugin version shows 4.1.3 or higher after updating
- Test that the Contact Form 7 PDF generation functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6316 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-6316 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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