CVE-2025-64231
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in RedefiningTheWeb WordPress Contact Form 7 PDF, Google Sheet & Database rtwwcfp-wordpress-contact-form-7-pdf allows Using Malicious Files.This issue affects WordPress Contact Form 7 PDF, Google Sheet & Database: from n/a through <= 3.0.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 confidenceThe WordPress plugin 'Contact Form 7 PDF, Google Sheet & Database' has an unrestricted file upload vulnerability (CWE-434) in versions through 3.0.0. The plugin fails to properly validate uploaded file types, allowing attackers to upload malicious files (such as PHP scripts) to the server. This could enable remote code execution and complete system compromise.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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.
-
Check plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find 'Contact Form 7 PDF, Google Sheet & Database', and read the version number displayed below the plugin name. Alternatively, check the plugin's main PHP file (usually in wp-content/plugins/contact-form-7-pdf-google-sheet-database/ or similar) for the 'Version' header in the plugin comment block.Affected if The installed version is 3.0.0 or lower (any version through 3.0.0 is affected)
-
Verify plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and confirm whether the 'Contact Form 7 PDF, Google Sheet & Database' plugin is currently activated.Affected if The plugin is active and the version is 3.0.0 or lower
-
Inspect upload directory for suspicious filesCheck the wp-content/uploads/ directory (or custom upload path if configured) for newly created files with executable extensions such as .php, .phtml, .php5, .php7, .exe, or .sh. Use file manager or command line: ls -la /path/to/wp-content/uploads/ and search for these extensions.Affected if Any unexpected PHP, phtml, or executable files are found in upload directories, indicating possible exploitation
-
Review recent server access logsExamine web server access logs (usually in /var/log/nginx/ or /var/log/apache2/) for POST requests to upload endpoints related to this plugin. Look for requests uploading files with executable extensions to paths containing 'upload' or 'cf7' or 'contact-form-7-pdf'.Affected if Logs show uploads of .php, .phtml, or other executable file types to the plugin's upload functionality
You are affected if the 'Contact Form 7 PDF, Google Sheet & Database' plugin is active at version 3.0.0 or lower, or if suspicious executable files exist in your upload directories.
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.
From vendor dataUpdate the plugin to version 3.0.1 immediately. Until the update is applied, consider disabling the plugin, removing write permissions on upload directories, or deploying WAF rules to block executable file extensions (.php, .phtml, .exe, etc.) in upload paths.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64231 — 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-2025-64231 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