CVE-2026-57799
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 Nuss nuss allows PHP Local File Inclusion.This issue affects Nuss: from n/a through <= 1.3.6.
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 confidenceLocal File Inclusion (LFI) vulnerability in uxper Nuss allows attackers to include arbitrary local files via unsanitized input in PHP include/require statements. This can lead to exposure of sensitive files, source code disclosure, or potentially remote code execution depending on file contents.
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 Nuss is installedSearch the web root directory for files named 'nuss', 'uxper', or application-specific folders. Look for composer.json, package.json, or any configuration files that indicate the uxper Nuss application.Affected if The application files are present on the system
-
Determine the installed versionCheck version files such as version.php, composer.json with 'uxper' or 'nuss' in the name, or any CHANGELOG/README files within the application directory. Compare the found version against any official version releases.Affected if The installed version matches or precedes the affected version range published by the vendor
-
Locate PHP file inclusion functionsSearch the codebase for PHP include, require, include_once, or require_once statements, particularly those that concatenate or directly use variable parameters in the file path.Affected if Dynamic file inclusion using variables is present in the application code
-
Inspect file path parameters in HTTP requestsReview the application source code for parameters that accept file paths or filenames as input. Check route definitions or parameter handlers that pass user input to file inclusion functions.Affected if User-supplied input is directly used in include/require statements without sanitization
-
Verify if the vulnerable endpoint is exposedIdentify and test web endpoints that accept file path parameters. These are typically found in routing logic that handles dynamic page loading or template inclusion.Affected if An endpoint accessible via HTTP accepts file path parameters and passes them to PHP inclusion functions
A user is affected if uxper Nuss is installed, the version is within the vulnerable range, and the application exposes file path parameters that can be manipulated to include arbitrary local files.
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 on file path parameters, use whitelist-based file inclusion, avoid user-supplied input in include/require statements, and consider migrating to a secure routing mechanism.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57799 — 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-57799 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