CVE-2026-34895
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 Softlab Core < 1.2.11 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 confidenceAn unauthenticated Local File Inclusion (LFI) vulnerability in Softlab Core versions prior to 1.2.11 allows remote attackers to access sensitive files on the server through path traversal in user-supplied input without requiring authentication.
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 Softlab Core installation and versionLocate the Softlab Core installation directory and check the version file or application metadata. Common locations include the application root directory, a version info file, or the admin panel version display.Affected if The installed version is lower than 1.2.11 (e.g., 1.2.10, 1.0.5, etc.)
-
Determine if file path parameter endpoints are exposedIdentify web endpoints or API routes in Softlab Core that accept file path parameters. Review application routing configuration or HTTP access logs for requests containing file path arguments.Affected if Endpoints accepting file path parameters are accessible without authentication and do not sanitize input for directory traversal sequences (e.g., ../, ..\)
-
Test for directory traversal vulnerabilitySend a crafted HTTP request to the suspected endpoint with directory traversal payloads such as ../../../../etc/passwd or ..\..\..\windows\system32\config\sam. Observe the HTTP response for file contents.Affected if The application returns file contents from outside the intended directory, indicating LFI is possible without authentication
You are affected if Softlab Core version is below 1.2.11 AND an unauthenticated endpoint accepting file path parameters is exposed and permits directory traversal.
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.
dbcve · scopedUpgrade Softlab Core to version 1.2.11 or later to obtain the vendor patch; if immediate upgrade is not feasible, implement web application firewall rules to block path traversal patterns (../) in request parameters.
1.2.11 or later
- Upgrade Softlab Core to version 1.2.11 or later to resolve the unauthenticated Local File Inclusion vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34895 — 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-34895 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