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

CVE-2023-25995

HIGH · 7.5 CVSS v3.1 Published 2025-06-06
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 choicehomemortgage AI Mortgage Calculator allows PHP Local File Inclusion. This issue affects AI Mortgage Calculator: from n/a through 1.0.1.

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 · moderate confidence

The AI Mortgage Calculator plugin for WordPress contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is used in include/require statements without proper sanitization. An unauthenticated attacker could potentially include arbitrary files from the server's filesystem, leading to information disclosure or code execution.

MitigationImplement strict input validation using a whitelist approach for file inclusion, or eliminate dynamic file inclusion entirely by using fixed includes. Never allow user input to control file paths in include/require statements.

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. Confirm AI Mortgage Calculator plugin is installed
    Navigate to WordPress admin > Plugins and look for 'AI Mortgage Calculator' in the installed plugins list, or inspect the /wp-content/plugins/ directory for an ai-mortgage-calculator folder
    Affected if The plugin folder 'ai-mortgage-calculator' exists in the plugins directory
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > AI Mortgage Calculator and read the version number from the plugin details, or open the main plugin PHP file and look for the 'Version' header in the plugin comment block
    Affected if The installed version matches or falls within any affected version range (compare your version to the affected releases)
  3. Locate the vulnerable file inclusion code
    Search the plugin directory for PHP files containing include, require, include_once, or require_once statements that use variables derived from user input (GET, POST, REQUEST parameters) without validation. Common patterns: include($_GET['file']), include($_REQUEST['template'])
    Affected if PHP files in the plugin contain dynamic include/require statements using unsanitized user-supplied parameters
  4. Verify the vulnerable parameter is accessible
    Check if the identified vulnerable file and parameter can be accessed without authentication by attempting a test request (e.g., ?file=../../../wp-config.php or similar path traversal attempt)
    Affected if The vulnerable file accepts user input via GET/POST/REQUEST without requiring authentication and without sanitizing path traversal characters
  5. Confirm plugin is active on the site
    In WordPress admin > Plugins, verify the AI Mortgage Calculator plugin shows as 'Active', or check the wp_options table for the active_plugins entry containing 'ai-mortgage-calculator'
    Affected if The plugin is currently activated and the vulnerable code is reachable

Your environment is affected if the AI Mortgage Calculator plugin is installed, active, and contains dynamic file inclusion code that uses unsanitized user input accessible to unauthenticated users.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation using a whitelist approach for file inclusion, or eliminate dynamic file inclusion entirely by using fixed includes. Never allow user input to control file paths in include/require statements.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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