CVE-2025-60078
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 Agence web Eoxia – Montpellier Task Manager task-manager allows PHP Local File Inclusion.This issue affects Task Manager: from n/a through <= 3.0.2.
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 confidenceThe Task Manager application by Eoxia contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is used in include/require statements without proper validation. An attacker could manipulate file path parameters to read sensitive server files or potentially execute arbitrary PHP code depending on server configuration.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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 if Eoxia Task Manager is installedSearch for Task Manager application files by Eoxia in the web root directory. Look for directories or files containing 'task manager', 'eoxia', or similar naming patterns.Affected if The Eoxia Task Manager application is present on the server.
-
Locate the installed versionExamine version files, config files, or header/comment sections in PHP files within the Task Manager installation for version strings like 'version X.X.X' or similar.Affected if The installed version cannot be determined or falls within an affected version range.
-
Identify PHP files with file inclusion functionsSearch the Task Manager source code for PHP files containing 'include', 'require', 'include_once', or 'require_once' statements where variables or parameters are used in the file path.Affected if PHP files use include/require with user-controllable input without validation.
-
Check for vulnerable parameter handlingExamine the identified file inclusion code paths to determine if URL parameters or POST data are directly used in include/require statements without sanitization functions like basename() or realpath().Affected if User-supplied input from GET/POST parameters is directly used in include/require statements without validation.
-
Verify PHP configuration settingsCheck the PHP configuration file (php.ini) or use phpinfo() to verify if allow_url_fopen and allow_url_include are enabled.Affected if allow_url_fopen or allow_url_include are enabled, increasing the exploitability of the LFI vulnerability.
The environment is affected if the Eoxia Task Manager application is installed and contains PHP code that uses user-supplied input in include/require statements without proper validation, allowing path traversal.
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 input validation and whitelist-based filtering on all file inclusion parameters, using basename() and realpath() functions to prevent directory traversal attacks. Ensure allow_url_fopen and allow_url_include are disabled in PHP configuration.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60078 — 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-60078 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