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

CVE-2025-60196

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 Clearblue Clearblue® Ovulation Calculator clearblue-ovulation-calculator allows PHP Local File Inclusion.This issue affects Clearblue® Ovulation Calculator: from n/a through <= 1.2.4.

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 vulnerability exists in the Clearblue Ovulation Calculator (versions up to 1.2.4) where user-supplied input is not properly validated before being used in include/require statements. This allows attackers to read sensitive local files from the server filesystem via directory traversal attacks.

MitigationImplement strict input validation and sanitization on all parameters used in include/require statements, and use allowlist validation for permitted files. Consider using basename() and realpath() to validate that requested files are within expected directories.

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 the Clearblue Ovulation Calculator installation
    Locate the application files on the web server. Check common web directories (htdocs, www, public_html) for a folder named 'clearblue', 'ovulation-calculator', or similar. Look for PHP files with 'clearblue' in the name or content.
    Affected if The application is present on the server in a web-accessible directory.
  2. Determine the installed version
    Check for a version file, readme.txt, or the main PHP file for a version number or release date. Common locations: version.php, config.php, or the main index.php may contain a version constant.
    Affected if The version is 1.2.4 or any lower version number.
  3. Locate PHP files using include or require with user input
    Search the application source code for patterns like 'include($_GET', 'require($_GET', 'include($_POST', 'require($_REQUEST' or similar constructions where user-supplied parameters are used directly in file inclusion statements.
    Affected if User-controlled parameters (from $_GET, $_POST, $_REQUEST) are used in include/require without validation.
  4. Check for lack of input sanitization on inclusion parameters
    Examine the include/require statements found in step 3. Look for the absence of sanitization functions such as basename(), realpath(), or allowlist validation before the file inclusion.
    Affected if The code passes user input directly to include/require without sanitization or validation.
  5. Verify directory traversal is possible
    Test the vulnerable parameter with a traversal sequence like ../../../../etc/passwd or ../../config.php in a test environment to confirm the LFI allows reading files outside the intended directory.
    Affected if The application returns content from files outside the intended directory when traversal sequences are used.

A user is affected if the Clearblue Ovulation Calculator version 1.2.4 or lower is installed and the application contains PHP code that uses unvalidated user input in include/require statements, allowing directory traversal.

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 and sanitization on all parameters used in include/require statements, and use allowlist validation for permitted files. Consider using basename() and realpath() to validate that requested files are within expected directories.

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-60196 — 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-60196 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