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-134 · Use of Externally-Controlled Format String

Use of Externally-Controlled Format String

Technical detail

In plain English

Use of Externally-Controlled Format String

What this can look like

An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.

A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.

The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.

MITRE description from the synchronized CWE record

The product uses a function that accepts a format string as an argument, but the format string originates from an external source.

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.