CVE-2025-69125
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 Food Drop <= 1.3 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 Food Drop version 1.3 and below allows remote attackers to read sensitive files from the server filesystem without authentication. The vulnerability likely stems from insufficient input validation on file inclusion parameters, enabling path 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Food Drop installation and versionLocate the Food Drop application directory and check for version information in config files, README, or the main application file (typically version.php, about.php, or similar).Affected if The installed version is 1.3 or lower.
-
Confirm file inclusion functionality existsExamine the application source code for file inclusion functions (include, require, include_once, require_once, readfile, file_get_contents) that process user input as file paths.Affected if The application uses dynamic file inclusion with user-supplied parameters without validation.
-
Identify vulnerable file inclusion parametersSearch the codebase for parameters that accept file paths or filenames (e.g., 'file', 'page', 'path', 'template', 'include') in GET or POST requests.Affected if Parameters accept raw file paths or filenames without sanitization.
-
Test for path traversal vulnerabilityIf the file inclusion endpoint is identified, attempt a test request with path traversal sequences (e.g., ../../../../etc/passwd) to verify if the application returns file contents.Affected if The application returns contents of files outside the webroot when path traversal sequences are used.
-
Check if application is exposed without authenticationVerify that the vulnerable file inclusion endpoints are accessible without requiring authentication (no login session required).Affected if The file inclusion functionality is accessible to unauthenticated users.
A defender is affected if Food Drop version 1.3 or below is installed and the application exposes file inclusion functionality accessible to unauthenticated users without proper input validation.
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 to a patched version of Food Drop. If no patch exists, implement strict input validation and whitelist-based file inclusion to prevent path traversal sequences.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69125 — 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-69125 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