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

CVE-2025-69143

HIGH · 8.1 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Unauthenticated Local File Inclusion in Mission <= 1.22 versions.

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

An unauthenticated Local File Inclusion (LFI) vulnerability exists in Mission software versions 1.22 and below. Attackers can exploit this by manipulating file path parameters to read sensitive files from the server's filesystem without any authentication credentials.

MitigationUpgrade Mission software to a version beyond 1.22 that includes the security patch, or implement strict input validation and path sanitization on all file-inclusion logic to prevent directory traversal attacks.

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

CVSS:3.1/AV:N/AC:H/PR:N/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. Determine installed Mission software version
    Locate the version identifier in the software installation directory, about page, or by querying the application's version endpoint/API if available
    Affected if Installed version is 1.22 or below (any version from initial release up to 1.22)
  2. Identify exposed file-inclusion functionality
    Review web application routing configuration and locate any endpoints or parameters that accept file path inputs (such as 'file', 'path', 'template', 'page', 'include', or similar file-referencing parameters)
    Affected if File path parameters are accessible without authentication on externally-facing endpoints
  3. Test for directory traversal in file parameters
    Send HTTP requests with traversal sequences (such as ../../../../etc/passwd or ..\..\..\windows\win.ini) to identified file-referencing parameters and observe if files outside the intended directory are returned
    Affected if Server returns content from files outside the expected directory, indicating LFI is possible
  4. Review web server access logs
    Examine web server logs (Apache access.log, Nginx access.log, or similar) for patterns containing '../' or encoded traversal sequences targeting sensitive system files

Environment is affected if Mission software version 1.22 or below is running AND unauthenticated file path parameters are accessible that allow directory traversal to read arbitrary files.

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

Upgrade Mission software to a version beyond 1.22 that includes the security patch, or implement strict input validation and path sanitization on all file-inclusion logic to prevent directory traversal attacks.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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