CVE-2025-58954
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 · uneditedUnauthenticated Local File Inclusion in HomeRoofer <= 2.11.0 versions.
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 confidenceUnauthenticated Local File Inclusion vulnerability in HomeRoofer versions 2.11.0 and below allows remote attackers to read sensitive files on the server filesystem without any authentication credentials.
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.
-
Identify installed HomeRoofer versionLocate the version file or check the application header/meta data - common locations include a version file in the installation directory, the About page in the web interface, or the HTTP response headers from the HomeRoofer serverAffected if The installed version is 2.11.0 or lower
-
Confirm web interface is externally accessibleVerify the HomeRoofer web interface is reachable over HTTP/HTTPS from the network. Check if port 80/443 or the configured web port is open and responds to requestsAffected if The web interface is reachable without authentication and the version is 2.11.0 or lower
-
Identify the file inclusion endpointReview the application routing/configuration to locate endpoints that accept file path parameters. Common patterns include endpoints with 'file', 'path', 'page', or 'include' in the URL parameter namesAffected if The application exposes a parameter that accepts file paths and the version is 2.11.0 or lower
-
Review access logs for directory traversal attemptsExamine web server access logs for requests containing '../' patterns or absolute file paths in query parameters, particularly targeting sensitive system files like /etc/passwd or Windows equivalentsAffected if Logs show successful directory traversal requests or the target endpoint returns content from files outside the web root
You are affected if HomeRoofer version 2.11.0 or below is installed and its web interface is accessible without authentication, as the LFI vulnerability allows unauthenticated file reads.
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 dataUpgrade HomeRoofer to a version newer than 2.11.0. If no patched version is available, implement input validation to block directory traversal patterns (e.g., ../) and restrict file access permissions on the web server.
- 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-58954 — 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-58954 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