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-89 · Improper Neutralization of Special Elements used in an SQL Command

Input can change the structure of a database query.

Important

In plain English

Input can change the structure of a database query.

What this can look like

A login or search field is joined directly into SQL, allowing an attacker to alter what the database query does instead of supplying ordinary data.

A search, filter, or login value changes the meaning of a database query and exposes or modifies records outside the intended scope.

An application builds a query from untrusted text, letting crafted input affect the query structure rather than only the supplied value.

MITRE description from the synchronized CWE record

The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

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.