dbcve.org
Path TraversalWeakness · CWE-22

CVE-2019-25295

MEDIUM · 6.5 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 →
74/100
Remediation priority · Elevated
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 Upload Directory Traversal in versions before 9.660 via the uploadFormFiles function. This allows attackers to overwrite any file with a whitelisted type on an affected site.

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 contains a directory traversal vulnerability in the uploadFormFiles function that allows attackers to manipulate upload paths using traversal sequences (e.g., '../'). This enables overwriting arbitrary files with whitelisted file types on the server, potentially leading to code execution if PHP files can be overwritten.

MitigationUpdate the WP Cost Estimation plugin to version 9.660 or later. If an update is unavailable, consider removing the plugin or implementing file upload validation that prevents directory traversal sequences in filenames.

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
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

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. Locate the WP Cost Estimation plugin installation
    Check your WordPress plugins directory (wp-content/plugins/) for a folder named 'wp-cost-estimation' or similar. Alternatively, in WordPress admin, go to Plugins > Installed Plugins and look for 'WP Cost Estimation' or 'Cost Estimation & Payment Forms'. Note the installed version number displayed there.
    Affected if The plugin is not found in the plugins directory or installed plugins list.
  2. Compare installed version to the fixed release
    If the plugin is found, note the exact version number shown (e.g., 9.650, 9.640). Compare this to version 9.660. You can also check the plugin's main PHP file (usually wp-cost-estimation/easy-content-templates/easy-wp.php or similar) for the version defined in the header comment.
    Affected if The installed version is lower than 9.660 (e.g., 9.650, 9.640, 9.63, etc.). Versions prior to 9.660 are affected.
  3. Identify if the upload form feature is active
    Check your WordPress pages/posts for any published form that uses the WP Cost Estimation plugin's functionality. Look for pages containing the shortcode [cost-estimation-form] or similar. Visit these pages to confirm the estimation form with file upload capability is publicly accessible.
    Affected if A cost estimation form with file upload is published and accessible to unauthenticated users.
  4. Verify the vulnerable upload endpoint exists
    Inspect the source of an active estimation form page. Look for a form element with action pointing to an endpoint like /wp-content/plugins/wp-cost-estimation/.../uploadFormFiles.php or similar. Manually access this URL or check if it responds to POST requests.
    Affected if The uploadFormFiles endpoint is reachable and responds to requests.

Your environment is affected if the WP Cost Estimation plugin is installed with a version lower than 9.660 AND a cost estimation form with file upload functionality is publicly accessible.

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 WP Cost Estimation plugin to version 9.660 or later. If an update is unavailable, consider removing the plugin or implementing file upload validation that prevents directory traversal sequences in filenames.

Recommended fix Moderate confidence

WP Cost Estimation plugin version 9.660 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'WP Cost Estimation' or 'WordPress Cost Estimation & Payment Forms Builder' plugin
  4. Click 'Update Now' if an update is available, or manually download version 9.660 or later from the WordPress plugin repository or CodeCanyon
  5. Verify the plugin is updated to version 9.660 or higher
  6. Review any uploaded files for unauthorized modifications since the vulnerability allows file overwrite
Caveat Review plugin settings after upgrade as minor configuration changes may occur with major version updates

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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