CyberKit

Common Weakness Enumeration

Also called CWE.

A catalog of software and hardware weakness types, the root causes behind CVEs.

What it is

A community-developed, MITRE-maintained taxonomy of weakness classes (such as buffer overflow, SQL injection, or improper authentication) that describe the kinds of flaws that lead to vulnerabilities. Where a CVE names a specific instance, a CWE names the category of mistake.

Why it matters

CWE lets teams reason about root causes and systemic patterns rather than one-off bugs, informing secure-coding standards, static-analysis rules, and trend reporting on which weakness classes recur.

In practice

Tagging a cluster of findings to the same CWE to show a recurring input-validation weakness across the codebase.

What to look for

  • The CWE behind each CVE you face.
  • Weaknesses that repeat in your own code.
  • The CWE Top 25 list.

Common mistake

Fixing CVEs one at a time. Fix the weakness class to prevent the next one.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Burp Suite Commercial

    An intercepting proxy for testing web apps by hand and with its scanner.

  • ZAP Open source

    An open source web app scanner and proxy, often run in CI pipelines.

  • Cloudflare WAF Commercial

    Blocks common web attacks at the edge while the code gets fixed.

Read next

Sources