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-200 · Exposure of Sensitive Information to an Unauthorized Actor

Information is revealed to someone who should not receive it.

Important

In plain English

Information is revealed to someone who should not receive it.

What this can look like

An unauthenticated status page exposes internal addresses, usernames, tokens, or configuration details that help an attacker understand the environment.

An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.

Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.

MITRE description from the synchronized CWE record

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

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.