dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2019-25296

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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 WP Cost Estimation plugin for WordPress is vulnerable to arbitrary file uploads and deletion due to missing file type validation in the lfb_upload_form and lfb_removeFile AJAX actions in versions up to, and including, 9.642. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected sites server which may make remote code execution possible. Additionally, the attacker can also delete files on the server such as database configuration files, subsequently uploading their own database files.

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 WP Cost Estimation plugin for WordPress versions up to 9.642 lacks file type validation in the lfb_upload_form and lfb_removeFile AJAX actions, allowing unauthenticated attackers to upload arbitrary files (enabling RCE) and delete any file on the server.

MitigationUpdate the plugin to version 9.643 or later which includes proper file type validation and authentication checks. If immediate update is not possible, disable the affected AJAX actions or restrict them to authenticated users via hooks.

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

CVSS:3.1/AV:N/AC:L/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. Confirm WP Cost Estimation plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'wp-cost-estimation', 'cost-estimation', or similar. Also check the plugins list in WordPress admin under Plugins > Installed Plugins.
    Affected if The plugin folder exists in the WordPress installation
  2. Check installed plugin version
    Open the main plugin PHP file (usually in the plugin folder root) and locate the version comment in the file header, or check readme.txt for the 'Stable tag' version number.
    Affected if The version number is 9.642 or lower, or if the version cannot be determined but the plugin is present
  3. Verify AJAX actions are publicly accessible
    Inspect the plugin source code for registered AJAX actions. Look for 'wp_ajax_lfb_upload_form' and 'wp_ajax_lfb_removeFile' (or 'wp_ajax_nopriv_' variants). Check if these actions are hooked to 'wp_ajax_nopriv_' which makes them accessible to unauthenticated users.
    Affected if The vulnerable actions are hooked to wp_ajax_nopriv_ or have no authentication check, making them accessible without login
  4. Confirm file upload form is enabled on a site page
    Check WordPress pages/posts for usage of the plugin's shortcode (typically [cost_calculator] or similar) or look for enabled upload fields in the plugin's form builder/settings.
    Affected if The estimation form with file upload capability is published and accessible on a live page

The site is affected if the WP Cost Estimation plugin versions 9.642 or lower are installed AND the lfb_upload_form/lfb_removeFile AJAX actions are exposed to unauthenticated users AND the file upload feature is enabled on a published page.

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 plugin to version 9.643 or later which includes proper file type validation and authentication checks. If immediate update is not possible, disable the affected AJAX actions or restrict them to authenticated users via hooks.

Recommended fix Moderate confidence

Version 9.643 or later (latest available version from WordPress plugin repository)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'WP Cost Estimation' or 'Cost Estimation & Payment Forms' plugin
  4. Check the current version installed
  5. If current version is 9.642 or lower, update to the latest available version
  6. Alternatively, upload the latest version from wordpress.org/plugins/wp-cost-estimation

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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