CVE-2026-57794
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 uxper Golo Framework golo-framework allows PHP Local File Inclusion.This issue affects Golo Framework: from n/a through <= 1.7.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 · moderate confidenceA PHP Local File Inclusion vulnerability exists in the uxper Golo Framework (version through 1.7.3) that allows attackers to manipulate filename parameters in include/require statements to access unauthorized local files. The CVSS 7.5 score indicates high exploitability with network-based attack vector and no authentication required.
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 uxper Golo Framework is presentSearch your codebase for files or directories containing 'golo' or 'uxper'. Check composer.json for golo-related packages, or look for theme/plugin headers referencing Golo.Affected if Your application contains the uxper Golo Framework
-
Determine the installed Golo Framework versionLocate the version information in composer.json within the golo framework directory, or search for a version.php or version.txt file. Compare your version against 1.7.3.Affected if The version is 1.7.3 or lower
-
Find PHP files using dynamic file inclusionSearch PHP files in your golo installation for patterns where include, require, include_once, or require_once use variables such as $_GET, $_POST, or $_REQUEST directly in the path. Use grep to find 'include\($_GET' or 'require\($_REQUEST'.Affected if User input from request parameters reaches include/require statements
-
Verify lack of input validation on file inclusionExamine the code around the vulnerable include/require calls found in step 3. Determine whether the parameter values are sanitized using basename(), path traversal checks, or whitelist validation before being used.Affected if File inclusion parameters accept path traversal sequences (..) or arbitrary file paths without validation
You are affected if you are running Golo Framework version 1.7.3 or lower and your codebase contains PHP files where user-supplied input controls filename parameters in include/require statements without proper 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 whitelist-based input validation for file inclusion paths, disable allow_url_include, use basename() to extract only the filename, and ensure user-supplied input cannot contain path traversal sequences (..) or alternate file schemes.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57794 — 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-57794 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