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-862 · Missing Authorization
A sensitive action lacks an authorization check.
Headline signal
CWE-862 · Missing Authorization
A sensitive action lacks an authorization check.
In plain English
A sensitive action lacks an authorization check.
What this can look like
A logged-in ordinary user directly calls an administrative operation because the application never verifies that the user has administrative rights.
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 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.