dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-1028

HIGH · 8.1 CVSS v3.1 Published 2025-02-05
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 Contact Manager plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the contact form upload feature in all versions up to, and including, 8.6.4. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible in specific configurations where the first extension is processed over the final. This vulnerability also requires successfully exploiting a race condition in order to exploit.

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 Contact Manager WordPress plugin (versions up to 8.6.4) lacks file type validation in its contact form upload feature, allowing unauthenticated attackers to upload arbitrary files. Successful exploitation requires exploiting a race condition, and RCE is only achievable on server configurations where the first file extension takes precedence over the final extension.

MitigationUpdate the Contact Manager plugin to version 8.6.5 or later. If immediate patching is not feasible, disable the file upload feature in contact forms and consider deploying a WAF rule to block unauthorized file uploads.

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. Verify Contact Manager plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate Contact Manager (or contact-manager). Check the version number displayed. Alternatively, check the plugin header in wp-content/plugins/contact-manager/contact-manager.php for 'Version:' value.
    Affected if Installed version is 8.6.4 or earlier
  2. Identify contact forms with file upload enabled
    Navigate to Contact Manager > Contact Forms (or similar section). Review each contact form configuration and identify which forms have a file upload field enabled. Check the form settings for any file upload/input field type.
    Affected if Any contact form has a file upload feature enabled
  3. Inspect server configuration for double extension handling
    Check web server (Apache/Nginx) configuration for how it handles files with multiple extensions (e.g., file.php.jpg). In Apache, check for 'FilesMatch' directives or mod_rewrite rules. In Nginx, check 'server' block for location/extension handling directives.
    Affected if Server processes the first extension (e.g., .php in shell.php.jpg) rather than the final extension, allowing potential RCE if arbitrary file upload succeeds

Environment is affected if Contact Manager plugin version 8.6.4 or earlier is installed AND at least one contact form has the file upload feature enabled, with the web server configured to prioritize the first file extension over the final extension.

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 Contact Manager plugin to version 8.6.5 or later. If immediate patching is not feasible, disable the file upload feature in contact forms and consider deploying a WAF rule to block unauthorized file uploads.

Recommended fix Moderate confidence

Contact Manager plugin version newer than 8.6.4 (check WordPress plugin repository for latest stable release)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Contact Manager' plugin
  4. Check if the current version is 8.6.4 or lower
  5. If vulnerable, click 'Update Now' to install the latest version
  6. Alternatively, download the latest version from the WordPress plugin repository and upload it manually
  7. Verify the update was successful by checking the plugin version after updating

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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