CVE-2025-48149
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in dedalx Cook&Meal cookandmeal allows PHP Local File Inclusion.This issue affects Cook&Meal: from n/a through <= 1.2.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 confidenceA Local File Inclusion (LFI) vulnerability in dedalx Cook&Meal (cookandmeal) version 1.2.3 and below allows attackers to manipulate filename parameters in PHP include/require statements to read arbitrary local files on the server. This occurs due to insufficient input validation on user-controlled parameters used in file inclusion functions.
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.
-
Confirm Cook&Meal installationLocate the cookandmeal application on the server - look for directories named 'cookandmeal', 'Cook&Meal', or similar, and check for PHP files containing 'cookandmeal' or 'dedalx' in the codebaseAffected if The application is installed and running on the server
-
Identify installed versionCheck version.php, composer.json, or any version file within the cookandmeal installation directory for a version numberAffected if The installed version is 1.2.3 or any version lower than 1.2.3
-
Locate PHP file inclusion functionsSearch PHP source files for include, require, include_once, or require_once statements that accept user-supplied parameters (e.g., from $_GET, $_POST, or $_REQUEST)Affected if File inclusion functions use user input without proper validation
-
Check input validation on file parametersInspect the code handling file inclusion parameters - verify whether basename() and realpath() functions are used to sanitize the input, or if the code relies solely on the user-supplied valueAffected if User-controlled parameters are used directly in include/require without sanitization using basename() or realpath()
-
Test parameter manipulabilityIf identified, attempt to modify the file inclusion parameter (e.g., via GET/POST request) with paths like ../../../../etc/passwd to see if arbitrary files can be readAffected if The server returns content from files outside the intended directory
A user is affected if Cook&Meal version 1.2.3 or lower is installed and PHP file inclusion functions use unsanitized user input for filename parameters.
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 dataImplement strict whitelist-based validation on all parameters used in include/require statements, using basename() and realpath() functions to sanitize file paths and ensure only allowed files within an approved directory can be included.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48149 — 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-48149 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