Scantide
  MITRE CWE, explained by Scantide

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.

Scantide does not hide the technical detail. The attention labels below are a presentation aid: headline signals deserve immediate attention, important signals deserve review, and technical detail remains available without being allowed to drown out the stronger signals. A specific CVE can still make a normally secondary CWE much more serious.
984CWE records in local generation
51headline signals
316important signals
617technical-detail signals
Headline signalImportantTechnical detailCWE generation 20261112T072920Z-b834b5ede09d

CWE-732 · Incorrect Permission Assignment for Critical Resource

A critical resource receives permissions that are broader than intended.

Important

In plain English

A critical resource receives permissions that are broader than intended.

What this can look like

A service creates a sensitive file or object writable by ordinary users, allowing its contents or behavior to be changed.

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 specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

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.