CVE-2025-67254
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 · uneditedNagiosXI 2026R1.0.1 build 1762361101 is vulnerable to Directory Traversal in /admin/coreconfigsnapshots.php.
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 confidenceNagiosXI 2026R1.0.1 contains a directory traversal vulnerability in /admin/coreconfigsnapshots.php that allows attackers to access files outside the web root via path manipulation (e.g., ../ sequences). This could enable unauthorized reading of sensitive system files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2026CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 Nagios XI installation and versionCheck for Nagios XI by looking for /usr/local/nagiosxi/ or /opt/nagiosxi/ directories, or by querying the web server for the login page. Obtain the version from the admin dashboard or by examining version files in the Nagios XI installation directory.Affected if Nagios XI version 2026 (specifically 2026R1.0.1) is installed.
-
Verify coreconfigsnapshots.php existsCheck if the file /admin/coreconfigsnapshots.php exists in the web root. This can be done by attempting to access the URL (e.g., https://your-server/nagiosxi/admin/coreconfigsnapshots.php) or by examining the filesystem.Affected if The file exists and is accessible via the web server.
-
Confirm path traversal vulnerabilitySend a crafted HTTP request to /admin/coreconfigsnapshots.php with path traversal sequences such as ?file=../../../../etc/passwd or similar. Inspect the response to see if file contents outside the web root are returned.Affected if The application returns contents of files outside the web root directory (e.g., /etc/passwd, configuration files) when ../ sequences are used in the file parameter.
-
Check if admin module is accessibleVerify that the /admin/ endpoint is reachable. Test by accessing https://your-server/nagiosxi/admin/ and confirm authentication is required or the page loads.Affected if The admin interface is accessible without additional restrictions beyond normal authentication.
If Nagios XI version 2026 is installed and the coreconfigsnapshots.php endpoint responds to path traversal requests by leaking system files, the environment is affected by this CVE.
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 vendor patch when available; otherwise, implement strict input validation and path sanitization on the coreconfigsnapshots.php endpoint to restrict file access to allowed directories only.
- 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-2025-67254 — 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-67254 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