CVE-2025-69110
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 · uneditedUnauthenticated Local File Inclusion in AirSupply <= 2.0.0 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 confidenceUnauthenticated Local File Inclusion vulnerability in AirSupply version 2.0.0 and earlier allows remote attackers to read sensitive files on the server by manipulating file include parameters without authentication.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify AirSupply installationCheck your web server for the presence of AirSupply application files or check for AirSupply in your software inventory/dependency listAffected if AirSupply software is found in the environment
-
Determine AirSupply versionLocate the version file, About page, or API endpoint that exposes the AirSupply version number. Check the application's header, footer, or a /version or /about endpointAffected if The installed version is 2.0.0 or any version lower than 2.0.0
-
Locate file inclusion endpointReview application routing or proxy configurations to find endpoints that accept file path parameters (commonly seen as 'file', 'path', 'page', 'template', 'include', or 'lang' parameters in URLs)Affected if An endpoint accepting file path parameters is accessible without authentication
-
Test unauthenticated LFI accessSend a request to the suspected file inclusion endpoint with a benign path such as ../../../../etc/passwd or ../../../../windows/win.iniAffected if The server returns file contents from outside the web root directory without requiring login credentials
-
Verify directory traversal successCompare the HTTP response to expected file content. If the response contains user data from system files, the vulnerability is confirmedAffected if Arbitrary file reads succeed without any authentication token or session
The environment is affected if AirSupply version 2.0.0 or lower is installed and an unauthenticated file inclusion endpoint is accessible, allowing directory traversal to read arbitrary files.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade AirSupply to a version beyond 2.0.0 that includes the security patch; if immediate upgrade is not possible, implement strict input validation and disable allow_url_include in PHP configurations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69110 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-69110 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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