dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-53450

HIGH · 7.5 CVSS v3.1 Published 2025-09-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Pluginwale Easy Pricing Table WP easy-pricing-table-wp allows PHP Local File Inclusion.This issue affects Easy Pricing Table WP: from n/a through <= 1.1.3.

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 Pluginwale Easy Pricing Table WP plugin (easy-pricing-table-wp) versions through 1.1.3 contains a PHP Local File Inclusion (LFI) vulnerability. The plugin improperly validates file paths used in include/require statements, allowing attackers to manipulate the included file path to execute arbitrary PHP code from the local filesystem.

MitigationUpgrade to a patched version of Easy Pricing Table WP that properly validates and sanitizes file path inputs used in include/require statements, removing the ability to traverse directories or include arbitrary files.

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

CVSS:3.1/AV:N/AC:H/PR:L/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 Easy Pricing Table WP plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and locate 'Easy Pricing Table WP' or check the plugin directory wp-content/plugins/easy-pricing-table-wp/ for the presence of plugin files. Read the main plugin file header to confirm the version.
    Affected if The plugin is installed and its version is 1.1.3 or earlier.
  2. Identify file inclusion code paths
    Inspect the plugin PHP files in wp-content/plugins/easy-pricing-table-wp/ for include, include_once, require, or require_once statements that incorporate user-supplied input without sanitization. Search for patterns like 'include($_GET['...']' or 'require($var' in the plugin source code.
    Affected if Any include/require statement uses unsanitized request parameters or variables that can be controlled via HTTP requests.
  3. Check for path traversal vulnerabilities in file operations
    Review the identified inclusion code for lack of sanitization functions like basename(), realpath(), or allowlist validation. Determine if the code permits directory traversal sequences such as '../' in the file path parameter.
    Affected if The file path parameter accepts traversal sequences or arbitrary file paths without validation, allowing inclusion of files outside the intended directory.
  4. Confirm vulnerability exposure
    Test whether the vulnerable parameter is accessible to unauthenticated users by attempting HTTP requests with manipulated path values to the identified endpoint. Common vulnerable parameters include 'page', 'file', 'path', 'template', or 'include' in the query string.
    Affected if The vulnerable file inclusion functionality is accessible without authentication and accepts arbitrary file paths.

If the Easy Pricing Table WP plugin version is 1.1.3 or earlier and contains include/require statements using unsanitized user input that permits directory traversal, the installation is affected by this LFI vulnerability.

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

Upgrade to a patched version of Easy Pricing Table WP that properly validates and sanitizes file path inputs used in include/require statements, removing the ability to traverse directories or include arbitrary files.

Recommended fix Moderate confidence

Latest version available on wordpress.org (check for version > 1.1.3)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Easy Pricing Table WP' (easy-pricing-table-wp)
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. If no update is shown, manually download the latest version from wordpress.org and reinstall
  6. 6. Verify the plugin is running on the latest version after updating
Caveat Review plugin settings after upgrade as minor configuration changes may occur

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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