dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-14800

HIGH · 8.1 CVSS v3.1 Published 2025-12-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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 Redirection for Contact Form 7 plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'move_file_to_upload' function in all versions up to, and including, 3.2.7. This makes it possible for unauthenticated attackers to copy arbitrary files on the affected site's server. If 'allow_url_fopen' is set to 'On', it is possible to upload a remote file to the server.

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 Redirection for Contact Form 7 WordPress plugin is vulnerable to arbitrary file uploads in versions up to 3.2.7 due to missing file type validation in the move_file_to_upload function. Unauthenticated attackers can copy arbitrary files to the server, and with allow_url_fopen enabled, can upload remote files.

MitigationUpdate to the latest plugin version immediately. Disable allow_url_fopen in PHP configuration as a hardening measure and ensure proper file type validation is implemented in upload handlers.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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. Check if Redirection for Contact Form 7 plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Redirection for Contact Form 7' or inspect the plugin directory /wp-content/plugins/redirection-for-contact-form-7/ for the main PHP file
    Affected if The plugin is installed and active in WordPress
  2. Determine the installed plugin version
    Check the plugin header in the main PHP file (e.g., redirection-for-contact-form-7.php) for the 'Version' field, or view the plugin details in WordPress admin Plugins list
    Affected if The version number is 3.2.7 or lower (any version up to and including 3.2.7 is affected)
  3. Verify the vulnerable move_file_to_upload function exists
    Inspect the plugin source code for the move_file_to_upload function definition; this function handles file operations and lacks proper file type validation
    Affected if The function exists in the plugin code without proper file type validation checks
  4. Check PHP allow_url_fopen setting
    Create a PHP info page or run 'php -i' from command line, or check php.ini for the allow_url_fopen directive value
    Affected if allow_url_fopen is enabled (set to On), which allows remote file uploads as part of this attack vector

You are affected if the Redirection for Contact Form 7 plugin versions 3.2.7 or lower are installed and active, with the vulnerable move_file_to_upload function present, especially when allow_url_fopen is enabled in PHP.

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 to the latest plugin version immediately. Disable allow_url_fopen in PHP configuration as a hardening measure and ensure proper file type validation is implemented in upload handlers.

Recommended fix Moderate confidence

Version 3.2.8 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Redirection for Contact Form 7' in the plugin list
  4. Click 'Update now' if an update is available, or manually update to the latest version
  5. After updating, verify the plugin version is 3.2.8 or higher
  6. Review any recently uploaded files in the wp-content/uploads directory for suspicious content
  7. If compromise is suspected, audit the site for malicious files

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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