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-863 · Incorrect Authorization
An authorization check exists but makes the wrong decision.
Headline signal
CWE-863 · Incorrect Authorization
An authorization check exists but makes the wrong decision.
In plain English
An authorization check exists but makes the wrong decision.
What this can look like
A permission rule checks the wrong object or role and unintentionally allows one user to perform another user’s privileged action.
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 performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
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.