CVE-2025-26137
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 · uneditedSystemic Risk Value <=2.8.0 is vulnerable to Local File Inclusion via /GetFile.aspx?ReportUrl=. An unauthenticated attacker can exploit this issue to read arbitrary system files by supplying a crafted file path, potentially exposing sensitive information.
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 · high confidenceLocal File Inclusion vulnerability in Systemic Risk Value <=2.8.0 GetFile.aspx endpoint. The ReportUrl parameter accepts unvalidated path input allowing unauthenticated attackers to read arbitrary files on the server filesystem via path traversal sequences (e.g., ../../../etc/passwd).
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<= 2.8.0CVSS 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 Systemic Rm Risk Value installation and versionLocate the application installation directory and check the version manifest, assembly info, or version file. Common locations include the web root folder, an 'About' page, or the application's configuration files.Affected if The installed version is Systemic Rm Risk Value version 2.8.0 or lower.
-
Locate the GetFile.aspx endpointSearch the web root directory for GetFile.aspx. Common paths include /pages/, /handlers/, or the root directory. Also check for URL patterns like /GetFile.aspx, /api/GetFile.aspx, or similar variants.Affected if The GetFile.aspx file exists in the application's web directory.
-
Verify ReportUrl parameter availabilityAccess the GetFile.aspx page directly via HTTP/HTTPS request (e.g., GET /GetFile.aspx?ReportUrl=test). Check if the page accepts a 'ReportUrl' parameter and returns a response.Affected if The endpoint accepts a 'ReportUrl' parameter without requiring authentication.
-
Test for path traversal vulnerabilitySend a crafted request to GetFile.aspx with path traversal in the ReportUrl parameter (e.g., ../../../etc/passwd or ../../../windows/win.ini). Observe if the server returns file contents outside the intended directory.Affected if The ReportUrl parameter allows path traversal sequences and returns arbitrary file contents from the server filesystem.
A system is affected if it runs Systemic Rm Risk Value version 2.8.0 or lower with the GetFile.aspx endpoint exposed and the ReportUrl parameter accepting unauthenticated path traversal requests.
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 to patched version >2.8.0; implement strict input validation and whitelist-based file access controls on the GetFile.aspx endpoint to block path traversal attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26137 — 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-26137 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