CVE-2026-32392
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 Creatives_Planet Greenly greenly allows PHP Local File Inclusion.This issue affects Greenly: from n/a through <= 8.1.
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 the Greenly PHP application (version <= 8.1) allows attackers to read arbitrary files on the server by manipulating file include/require statements. This occurs due to insufficient input validation on file path parameters, potentially exposing sensitive system files, configuration data, and source code.
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 Greenly PHP installation and versionSearch the webroot for Greenly PHP application files (index.php, common config files) and check version.php or VERSION file for version numberAffected if Version number is 8.1 or lower
-
Locate file inclusion codeSearch source code for include, require, include_once, require_once statements that accept variable input (e.g., include($var), require($_GET['page'])Affected if File inclusion functions use variables or parameters without sanitization
-
Identify user-controlled file path parametersReview GET/POST parameters used in include/require calls; check if parameter values flow directly to file inclusion without validationAffected if User-supplied parameters are used in file inclusion without sanitization functions like basename() or whitelist checks
-
Test for directory traversal vulnerabilityAttempt to access known system files via suspected LFI parameters (e.g., ../../etc/passwd or ../../windows/win.ini); if application returns file contents, vulnerability is presentAffected if Application returns contents of files outside the intended directory when using ../ sequences
-
Check for sensitive file exposureAttempt to read configuration files (config.php, .env, database credentials) via the LFI parameterAffected if Application exposes sensitive configuration or source code files
User is affected if Greenly PHP version 8.1 or lower is installed AND user-controllable input flows directly into include/require statements without 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 dataImplement strict input validation and whitelisting for file inclusion paths, use basename() to strip directory traversal sequences (..), and avoid using user-supplied input directly in include/require statements.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32392 — 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-2026-32392 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