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

CVE-2025-39462

HIGH · 7.5 CVSS v3.1 Published 2025-04-17
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 teamzt Smart Agreements smart-agreements allows PHP Local File Inclusion.This issue affects Smart Agreements: from n/a through <= 1.0.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

A PHP Local File Inclusion (LFI) vulnerability in teamzt Smart Agreements <= 1.0.3 allows attackers to manipulate file inclusion parameters to include arbitrary PHP files from the server, potentially leading to remote code execution.

MitigationImplement strict input validation on file inclusion parameters, whitelist allowed files/directories, and disable allow_url_include. Consider using a whitelist approach for any dynamic file inclusion functionality.

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. Locate teamzt Smart Agreements installation and determine version
    Search the web server document root for teamzt Smart Agreements files (common paths: /var/www/html, /home/*/public_html, C:\inetpub\wwwroot). Look for version indicators in source code, config files, or README files. Check for a version.php, version.txt, or similar version file within the application directory.
    Affected if The installed version is 1.0.3 or lower, or no version can be determined (assume affected)
  2. Identify PHP file inclusion functionality
    Search the application source code for include, require, include_once, or require_once statements that use variables in the file path (e.g., include($_GET['file']). Use grep or a code search tool to find patterns like 'include($' or 'require($_' within PHP files in the application directory.
    Affected if File inclusion functions are used with potentially user-supplied input without proper sanitization
  3. Locate the vulnerable parameter endpoint
    Identify HTTP request points (GET/POST parameters) that control the file inclusion. Review PHP files that handle the include/require statements found in the previous step. Determine which parameter name controls the included file path (commonly: file, page, path, template, or similar).
    Affected if A parameter exists that allows direct or indirect control of the file path passed to PHP inclusion functions
  4. Test for LFI vulnerability (passive observation only)
    If you have authorized access, observe whether the application allows traversal sequences (../) in the identified parameter. Attempt to include a known safe file (e.g., /etc/passwd or a non-PHP file) using the parameter. Document the behavior without exploiting the vulnerability.
    Affected if The application accepts directory traversal sequences and includes files outside the intended directory, or returns file contents in the response
  5. Check for signs of prior exploitation
    Look for unexpected PHP files in the application directory, especially in upload or include folders. Search for known webshell patterns (base64_decode, shell_exec, system, passthru). Review web server access and error logs for unusual include/require requests with traversal patterns.
    Affected if Unexpected PHP files exist that were not part of the original installation, or logs show suspicious file inclusion requests

You are affected if teamzt Smart Agreements version 1.0.3 or lower is installed AND the application uses PHP file inclusion functions with user-controllable parameters that are accessible via HTTP requests.

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 on file inclusion parameters, whitelist allowed files/directories, and disable allow_url_include. Consider using a whitelist approach for any dynamic file inclusion functionality.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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