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-285 · Improper Authorization
The product authenticates a user but does not correctly verify permission for an action.
Headline signal
CWE-285 · Improper Authorization
The product authenticates a user but does not correctly verify permission for an action.
In plain English
The product authenticates a user but does not correctly verify permission for an action.
What this can look like
A normal authenticated account can call an administrative endpoint because the authorization check is missing or incorrect.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
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.