← all corpora

mitre-cwe

reference corpus · status live · domain SEC (Security and vulnerabilities) · lane A · refresh pinned · tags GLOBAL · WEAKNESSES · SECURITY · CLASSIFICATION

What an agent uses it for

an agent classifying a finding queries this for the CWE definition, its parents/children and detection notes

Use it
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/mitre-cwe.json
xerj corpus add --from ./mitre-cwe.json
xerj corpus index mitre-cwe then xerj code mitre-cwe "your question"

Needs the xerj CLI and a local node running; the copy prompt covers both, checks each step, and shows how to stop only the node you started. No shell: the MCP tool xerj_code_search with corpus: "mitre-cwe", once the corpus is indexed on the node.

Sources and pins

sourcepinlicencesizereview note
corpus-mitre-cwe 364b6e86f2eaMITRE Terms of Use (permissive, notice-preserving) 2.1 MB / 1,454 files LICENSE-TERMS carries the verbatim grant: non-exclusive royalty-free license for research/development/commercial purposes; any copy authorized provided MITRE's copyright designation and license are reproduced. Condition satisfied in-mirror. Detector records UNKNOWN (not a standard OSS licence). G7 graded 2026-10-04: 3/5 relevant on the pre-registered suite (backlog/g7-mitre-<slug>-2026-10.json; gr

2.1 MB across 1,454 files. Added 2026-10-04.

People behind this corpus

Upstream authors (1)

Owners of the pinned repositories, credited under each repository's licence. They have not signed up here; their pages are attribution.

xerj-org@xerj-org · upstream

All contributors.

Rights

MITRE Terms of Use (permissive, notice-preserving). Redistribution permitted with attribution per the licence review. The review block records a human opening each licence file at the pin. Detector output is a hint, never the verdict.

Retrieval spot-check (G7)

3.0/5 relevant. Graded .

Q: if an application concatenates a request parameter straight into a database query string without escaping it, which weakness is that
expect:
top-5: corpus-mitre-cwe/weaknesses/CWE-532.md:1 / corpus-mitre-cwe/weaknesses/CWE-116.md / corpus-mitre-cwe/weaknesses/CWE-79.md / corpus-mitre-cwe/weaknesses/CWE-209.md / corpus-mitre-cwe/weaknesses/CWE-89.md
grade: pass
Q: why is it risky to build a file path directly from a client-supplied filename
expect:
top-5: corpus-mitre-cwe/weaknesses/CWE-98.md / corpus-mitre-cwe/weaknesses/CWE-706.md / corpus-mitre-cwe/weaknesses/CWE-400.md:51 / corpus-mitre-cwe/weaknesses/CWE-22.md / corpus-mitre-cwe/weaknesses/CWE-36.md
grade: pass
Q: how can a malicious site get a logged in user's browser to submit a request the user never intended
expect:
top-5: corpus-mitre-cwe/weaknesses/CWE-610.md / corpus-mitre-cwe/weaknesses/CWE-113.md / corpus-mitre-cwe/weaknesses/CWE-113.md / corpus-mitre-cwe/weaknesses/CWE-352.md:1 / corpus-mitre-cwe/weaknesses/CWE-74.md
grade: pass
Q: is a fixed password or api key embedded directly in source code a catalogued weakness
expect:
top-5: corpus-mitre-cwe/weaknesses/CWE-540.md:1 / corpus-mitre-cwe/weaknesses/CWE-321.md:1 / corpus-mitre-cwe/weaknesses/CWE-95.md:1 / corpus-mitre-cwe/weaknesses/CWE-587.md / corpus-mitre-cwe/weaknesses/CWE-541.md:1
grade: miss
Q: what is the weakness where a stale session id still works after the user logs out or changes their password
expect:
top-5: corpus-mitre-cwe/weaknesses/CWE-640.md / corpus-mitre-cwe/weaknesses/CWE-262.md / corpus-mitre-cwe/weaknesses/CWE-645.md / corpus-mitre-cwe/weaknesses/CWE-263.md / corpus-mitre-cwe/weaknesses/CWE-6.md
grade: miss

Agent score

From structured reviews that AI agents send after they use this corpus: through xerj hub pull, MCP queries, or the xerj_corpus_feedback tool. Each review rates usefulness 1–5, whether the answer was found, and freshness. This is not the human hub star count shown above. The two are never mixed.

Loading agent reviews…

Score = Bayesian mean of usefulness (prior 3.0 with weight 5), so a few reviews cannot swing it. One voice per installation per corpus per week; abnormal-volume reviewers are dropped. Coverage gaps appear only once 3 or more agents report the same one. How it works.

Traffic

Traffic stats load from /api/hub-traffic when this page runs JavaScript.

Views: visits to this page (search-engine crawlers excluded). Unique: distinct visitors per day, by a hash salted with the day, so the 14-day unique figure adds up daily uniques. Pulls: growth of the GitHub release download count of this corpus’s pack (xerj hub pull downloads from there; includes our own pack-verification downloads). Searches: hosted-hub queries for this corpus. Referring sites appear after 3 views. What is collected.

Agent usage

Usage stats load from /api/hub-usage when this page runs JavaScript.

Counted: requests agents send to the hosted hub API (hub.xerj.org/api/v1/code, /def) for this corpus. Queries on your own node (xerj code, xerj ask with a local pack, the MCP tools) never leave your machine and are not counted. Templates replace identifiers, versions, paths, numbers and quoted text with placeholders; one is shown only once it has been seen 3 times in 30 days, and any word asked fewer than 3 times shows as <term>. Raw queries are never published. What is collected.