CVE-2026-31913
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Whitebox-Studio Scape scape allows Path Traversal.This issue affects Scape: from n/a through < 1.5.16.
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 confidenceA path traversal vulnerability in Whitebox-Studio Scape allows attackers to access files outside the restricted directory by manipulating file paths with '..' sequences. The vulnerability affects all versions of Scape prior to 1.5.16, and the high CVSS score indicates significant potential for unauthorized file system access.
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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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 Scape installation and versionLocate the Scape application and retrieve its version number (typically available via the application's About page, a --version flag, or a version file in the installation directory)Affected if The installed version is any version prior to 1.5.16 (e.g., 1.5.15, 1.5.0, 1.4.x, etc.)
-
Confirm Scape is running a web-facing componentInspect running processes or service configurations to determine if Scape's HTTP server or file serving module is active and bound to a network interfaceAffected if The HTTP/file serving component is enabled and accessible over the network (localhost or remote)
-
Verify file path handling is in useReview Scape's configuration files or logs for file access operations, upload features, or any endpoint that accepts file path parametersAffected if The application handles user-supplied file paths or serves files from a configurable directory
-
Test for path traversal exposureIf you have access to a file-related endpoint, attempt a request with a path containing '..' sequences (e.g., /../../etc/passwd) to observe whether the application returns files outside the intended directoryAffected if The application returns files from outside the restricted directory when '..' sequences are used in the request path
A user is affected if Scape version is prior to 1.5.16 AND the file serving/path handling feature is enabled and accessible.
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 Scape version 1.5.16 or later. Additionally, implement strict input validation and canonicalization of file paths to prevent traversal attempts.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31913 — 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-31913 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