# Cve Poc Generator

> Generate or adapt Proof-of-Concept (PoC) exploits for known CVEs from public sources. Search ExploitDB, GitHub advisories, Metasploit modules, and Nuclei templates; adapt payloads to the target's specific component version; ensure PoC is reproducible and safe (read-only where possible). Use after fingerprinting identifies a known vulnerable version.

- Skill: `wufufu770/cve-poc-generator-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add wufufu770/cve-poc-generator-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/wufufu770/cve-poc-generator-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- License: Apache-2.0
- Author: wufufu770 (https://skillmd.com/u/wufufu770)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/wufufu770/cve-poc-generator-2

---


## TL;DR

- **目的**：Generate or adapt PoC exploits for known CVEs
- **适用**：已知 CVE 的复现（用于报告）
- **输入**：CVE 编号 + 目标组件版本
- **输出**：可复现 PoC + 利用步骤 + 风险评估
- **红线**：仅用于授权测试；不传播 0-day
- **关联**：上游：component-nday → 下游：fp-check, reporting



## When to Use

- Target presents indicators of the vulnerability class this skill covers
- Fingerprint or recon indicates the relevant technology stack is in use
- Authorized testing scope covers the target endpoint or component
- Findings need to be validated through this skill's methodology

## When NOT to Use

- Target is clearly outside this skill's scope (refer to related skills)
- No authorization for testing
- Need a different category of testing (use related skills)
## Workflow

1. **Identify CVE** — From component fingerprint
2. **Search sources** — ExploitDB, GitHub, Packet Storm, Metasploit
3. **Select PoC** — Read-only preferred, full-RCE only with approval
4. **Adapt** — Match target version, environment
5. **Test in isolation** — Never on production
6. **Verify** — Cross-validate with fp-check
7. **Document** — Screenshot, request/response, time



## Advanced Techniques

### ExploitDB Search Strategy
Search ExploitDB by EDB-ID, CVE, or keywords. Verify PoC is for exact component version (not just family).

### PoC Adaptation
When no direct PoC exists, use Metasploit module (search type:exploit name:cve) + manual crafting based on CVE description.

### Safe Exploitation
Always run PoC in isolated VM first. Use `strace`/`ltrace` to understand what PoC does before running on production target.

### Multi-Stage Exploits
Some CVEs require chain: e.g., SSRF → IMDSv1 → IAM creds. Use one skill's output as another's input.