Software weaknesses, explained simply
CWE names recurring weakness types found in software and devices; it is not a list of individual vulnerabilities. Scantide keeps the MITRE terminology visible, then explains what each weakness means and shows familiar, non-operational examples of what it can look like in a real product.
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory
User-controlled path components can escape the intended directory.
Important
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory
User-controlled path components can escape the intended directory.
In plain English
User-controlled path components can escape the intended directory.
What this can look like
A download endpoint expects a filename, but crafted path segments make it read a configuration or credential file outside the download folder.
A request intended to access one application file is manipulated so it reaches a configuration, key, or system file outside the permitted folder.
An archive, download, import, or file-management feature accepts a path that escapes the directory the application meant to restrict it to.
MITRE description from the synchronized CWE record
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Examples are intentionally conceptual. They explain the security consequence without providing exploit payloads or step-by-step attack instructions. MITRE remains the authoritative source for the CWE definition and mapping guidance.