CVE-2026-30480
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 · uneditedA Local File Inclusion (LFI) vulnerability in the NFSen module (nfsen.inc.php) of LibreNMS 22.11.0-23-gd091788f2 allows authenticated attackers to include arbitrary PHP files from the server filesystem via path traversal sequences in the nfsen parameter.
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 confidenceLibreNMS contains a Local File Inclusion vulnerability in the NFSen module (nfsen.inc.php) where the nfsen parameter accepts path traversal sequences (e.g., ../../), allowing authenticated attackers to read and include arbitrary PHP files from the server filesystem. Successful exploitation could lead to sensitive data disclosure or remote code execution if the attacker can control the contents of included files.
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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 LibreNMS installationLocate the LibreNMS installation directory (commonly /opt/librenms or /var/www/html/librenms). Run: find / -type d -name 'librenms' 2>/dev/null | head -5Affected if LibreNMS is installed on the server
-
Check LibreNMS versionView the version file within the installation directory. Run: cat /path/to/librenms/librenms.php 2>/dev/null | grep -i 'version' or check composer.json for the version numberAffected if The installed version has not been patched for this vulnerability (compare to any official advisory version)
-
Verify NFSen module presenceCheck if the NFSen module file exists. Run: find /path/to/librenms -name 'nfsen.inc.php' 2>/dev/nullAffected if The file nfsen.inc.php exists in the LibreNMS installation
-
Confirm NFSen feature is enabledExamine the LibreNMS configuration for NFSen settings. Check /path/to/librenms/config.php for $config['nfsen_enable'] or similar NFSen-related entries, or view the module status in the web UI under ModulesAffected if NFSen module is enabled or configured in LibreNMS
-
Check web access to NFSen functionalityAttempt to access the NFSen module URL path in the web interface (typically /nfsen/ or check routes). Alternatively, inspect the application routing to confirm the nfsen parameter endpoint existsAffected if The NFSen endpoint is accessible and accepts the nfsen parameter
Your environment is affected if LibreNMS is installed with the NFSen module enabled, the nfsen.inc.php file exists, and the web interface exposes an endpoint that accepts the nfsen parameter without proper path traversal sanitization.
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 the nfsen parameter to reject path traversal sequences (../), use basename() to strip directory components, and consider whitelisting allowed NFSen configurations. Apply principle of least privilege to the authenticated user sessions.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30480 — 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-30480 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