vuln-kb

Map security testing signals to CWE vulnerability references and test strategies.

11|1|Updated May 4, 2026
One-click install
npx skills add https://github.com/dreadnode/capabilities --skill vuln-kb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vuln-kb
Source: https://github.com/dreadnode/capabilities/tree/main/capabilities/web-security/skills/vuln-kb
Command: npx skills add https://github.com/dreadnode/capabilities --skill vuln-kb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security testers and penetration testers often waste time manually searching for CWE details, attack playbooks, and detection signatures during web application and API security assessments, leading to inconsistent testing and missed vulnerabilities.

Core Features & Use Cases

  • Signal-to-Vulnerability Mapping: Quickly map common static analysis signals and HTTP traffic patterns (like dangerouslySetInnerHTML or GraphQL introspection requests) to high-priority vulnerability classes.
  • CWE Quick References: Access test strategies, detection signals, and reporting requirements for common vulnerability categories including injection, broken access control, SSRF, and CORS misconfigurations.
  • Systematic Analysis Frameworks: Use codified analysis lenses (taint analysis, trust boundary mapping, business logic tracing) and full testing checklists to ensure comprehensive coverage of web application and API attack surfaces.
  • Use Case: A tester finds a React application using dangerouslySetInnerHTML with user-controlled input; they can immediately look up the associated DOM XSS (CWE-79) test strategy, detection signals, and reporting standards without leaving their workflow.

Quick Start

Use the vuln-kb skill to look up the test strategy and detection signals for CWE-89 SQL Injection when you encounter SQL error messages in application responses.

Frequently Asked Questions about vuln-kb

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map static analysis signals to web vulnerability classes during penetration testing?

Web vulnerability mapping correlates static analysis signals and HTTP traffic patterns, such as dangerouslySetInnerHTML or GraphQL introspection requests, directly to high-priority vulnerability classes and associated CWEs for rapid triage.

What CWE references should I use for SSRF detection and CORS misconfiguration testing?

CWE references for SSRF detection and CORS misconfigurations provide specific test strategies, detection signals, and reporting requirements to validate access control and injection vulnerabilities during web application assessments.

How does taint analysis work for identifying XSS vulnerabilities in web applications?

Taint analysis for XSS vulnerabilities traces user-controlled input through application trust boundaries to identify dangerous sinks, mapping detection patterns like dangerouslySetInnerHTML to CWE-79 test strategies and validation steps.

Can I use this for systematizing API security testing checklists and reporting requirements?

Yes, API security testing is systematized through codified analysis lenses and full testing checklists that ensure comprehensive attack surface coverage and deliver standardized reporting requirements for vulnerability documentation.

What is the best way to triage SQL error messages found in application responses?

Triage SQL error messages by looking up the associated CWE-89 SQL Injection test strategy, which provides specific detection signals and validation techniques to confirm the vulnerability without leaving your workflow.

Does this vulnerability testing reference support business logic tracing for broken access control?

Yes, business logic tracing is included as a codified analysis lens to systematically evaluate broken access control vulnerabilities, mapping trust boundaries and application error messages to appropriate detection patterns.