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

CVE-2025-62075

HIGH · 7.5 CVSS v3.1 Published 2025-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 Ido Kobelkowsky Simple Payment simple-payment.This issue affects Simple Payment: from n/a through <= 2.4.6.

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

This is a PHP Remote File Inclusion (RFI) vulnerability in the Simple Payment plugin. The vulnerability allows remote attackers to include arbitrary files from external sources due to unsanitized user input being used directly in PHP include/require statements, potentially enabling remote code execution.

MitigationReplace dynamic file inclusion with static paths or implement strict allowlist-based input validation. Sanitize all user-supplied parameters before use in include/require statements, and disable allow_url_include if not required.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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. Identify if Simple Payment plugin is installed
    Search the web server document root for files or directories named 'simple-payment', 'simplepayment', or similar variants. Check both wp-content/plugins (for WordPress) or common plugin installation paths for the affected CMS/framework.
    Affected if The Simple Payment plugin files are found in the web-accessible directories.
  2. Determine the installed plugin version
    Locate the main plugin file (typically named plugin.php, index.php, or the plugin's primary PHP file) and read the version declaration in the file header comment or a dedicated version/config file.
    Affected if The installed version is any version of the Simple Payment plugin, as no safe version range was specified in the CVE advisory.
  3. Verify PHP allow_url_include setting
    Check the php.ini configuration file or run 'php -i' / 'phpinfo()' to inspect the 'allow_url_include' directive. This setting controls whether PHP can include files from remote URLs.
    Affected if allow_url_include is enabled (set to On), which is required for full Remote File Inclusion exploitation.
  4. Identify vulnerable include/require patterns
    Search the plugin source code for dynamic include(), require(), include_once(), or require_once() statements where user-supplied parameters (GET, POST, COOKIE, or REQUEST superglobals) are used directly without sanitization or validation.
    Affected if The plugin code contains include/require statements that use unsanitized user input (e.g., include($_GET['page']); or similar patterns).
  5. Check if vulnerable parameters are accessible
    Review the plugin's routing or entry points to determine if the affected parameters can be submitted via HTTP requests from untrusted sources (internet or untrusted network).
    Affected if The vulnerable parameter can be passed via HTTP GET or POST requests without authentication or CSRF protection.

Your environment is affected if the Simple Payment plugin is installed, uses vulnerable include/require patterns with user input, and (for full RFI) allow_url_include is enabled in PHP configuration.

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

Replace dynamic file inclusion with static paths or implement strict allowlist-based input validation. Sanitize all user-supplied parameters before use in include/require statements, and disable allow_url_include if not required.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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