CVE-2025-49894
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.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 Nuss versions up to 1.3.3 where include/require statements do not properly validate user-controlled input, allowing attackers to include arbitrary files from the server filesystem.
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.
-
Locate Nuss installation and determine versionSearch for Nuss PHP files (index.php, config files) and check version.php or VERSION file for version number. Compare against affected range: versions up to and including 1.3.3Affected if Installed Nuss version is 1.3.3 or lower
-
Identify include/require statements in source codeSearch PHP source files for include(), require(), include_once(), or require_once() statements that use variables in the path parameter (e.g., include($file))Affected if Code contains dynamic include/require statements using unsanitized user input
-
Verify user input reaches file inclusion functionsTrace the data flow from request parameters (GET/POST) to the include/require statements found. Check if parameters like 'page', 'file', 'path', or similar are passed directly to include without validationAffected if User-supplied input from HTTP requests is used in include/require statements without basename() or whitelist filtering
-
Test if arbitrary file inclusion is possibleSend HTTP requests with manipulated parameters (e.g., ?file=../../../../etc/passwd) to endpoints using include/require to see if local files can be includedAffected if The application returns content from arbitrary files outside the intended directory
-
Check PHP configuration for remote inclusion riskInspect php.ini for allow_url_fopen=On and allow_url_include=On settings which would allow remote file inclusion in addition to localAffected if allow_url_fopen or allow_url_include are enabled, increasing exploit severity
You are affected if running Nuss version 1.3.3 or lower AND your application uses include/require with user-controlled input that is not validated via basename() or whitelist filtering.
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 dataApply input validation using basename() and whitelist filtering on file inclusion paths; update to patched version if available; consider disabling allow_url_fopen/allow_url_include.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49894 — 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-49894 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