CVE-2025-58994
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 designervily Greenify greenify allows PHP Local File Inclusion.This issue affects Greenify: from n/a through <= 2.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 · moderate confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the Greenify application (version <= 2.2) that allows attackers to include arbitrary local PHP files through unsanitized user input, potentially leading to remote code execution or sensitive file disclosure.
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 Greenify installation and versionLocate the Greenify application directory and check for version information in the main PHP file, composer.json, or a VERSION file. Common locations include the web root or application subdirectory.Affected if The installed version is 2.2 or lower, or if no version can be determined but the application is present
-
Find PHP file inclusion functionsSearch the application source code for include, include_once, require, or require_once statements that use variables or user input without sanitization. Look for patterns like 'include($var)', 'require($_GET[...])', or dynamic includes using concatenation.Affected if Dynamic file inclusion using unsanitized user input (e.g., $_GET, $_POST, $_REQUEST) is found in the code
-
Identify the vulnerable endpointExamine the PHP file containing the insecure include statement to determine which HTTP parameter controls the file inclusion. Check for parameters that accept file paths or filenames.Affected if A parameter accepting user input is used directly in a file inclusion function without validation
-
Check PHP configuration for dangerous settingsReview php.ini or the application's PHP configuration for 'allow_url_include = 1' which would enable remote file inclusion in addition to local file inclusion.Affected if allow_url_include is enabled, increasing the severity of the vulnerability
-
Verify lack of input validationExamine the code around the include statement to check if basename(), realpath(), or allowlist validation is implemented before the file inclusion occurs.Affected if No input validation using basename(), realpath(), or an allowlist is present before the include statement
The environment is affected if Greenify version 2.2 or lower is installed AND the application contains PHP file inclusion logic using unsanitized user input.
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 dataRemediate by implementing strict input validation using allowlists, basename(), and realpath() functions to ensure included files are within expected directories, and disable allow_url_include in PHP configuration.
- 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-58994 — 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-58994 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