[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DFPJAE4V15BNQJEJV18A3P":3,"skill-same:01M7DFPJAE4V15BNQJEJV18A3P":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":14,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M7DFPJAE4V15BNQJEJV18A3P","cve",null,"Known CVE exploitation — fingerprint CMS\u002Fframework\u002Fplugin version, discover candidate CVE IDs (cve_by_package for ecosystem packages, cve_by_product for CMS\u002Fframework core), score them via cve_lookup, retrieve PoCs via research_cve, adapt the public exploit to the target, and confirm RCE. Use whenever the challenge tag is `cve`, recon fingerprinted a versioned service, or the challenge name hints at known vulnerable software (WordPress, Joomla, Apache Struts, Spring4Shell, Log4j, etc.).","Akapi895\u002Fraptix","Akapi895","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F83953516?v=4","01M7DEGNDGERR4F4YETDFVA512","Phạm Anh Tuấn","01M7DEGNEHYZNA920AYM5EH7H8",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FAkapi895\u002Fraptix\u002Fblob\u002Fmaster\u002Fpackages\u002Fraptix-skills\u002Fraptix_skills\u002Fdefs\u002Fstandard\u002Fexploit\u002Fweb\u002Fcve\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cve\ndescription: \"Known CVE exploitation — fingerprint CMS\u002Fframework\u002Fplugin version, discover candidate CVE IDs (cve_by_package for ecosystem packages, cve_by_product for CMS\u002Fframework core), score them via cve_lookup, retrieve PoCs via research_cve, adapt the public exploit to the target, and confirm RCE. Use whenever the challenge tag is `cve`, recon fingerprinted a versioned service, or the challenge name hints at known vulnerable software (WordPress, Joomla, Apache Struts, Spring4Shell, Log4j, etc.).\"\nallowed-tools: Bash Read Write\nmetadata:\n  subdomain: execution\n  when_to_use: \"cve, CVE, known vulnerability, public exploit, version-specific, plugin vulnerability, CMS exploit, WordPress vulnerability, vulnerable software, patched, unpatched, joomla vulnerability, drupal vulnerability, apache struts, spring4shell, log4j, log4shell, exploit-db, public PoC, n-day exploit, cve_lookup, cve_by_package, cve_by_product, research_cve\"\n  tags: web-application, cve, known-exploit, n-day, public-poc\n  mitre_attack: T1190, T1203, T1059\n---\n\n# CVE \u002F Known-Exploit Methodology\n\nExploits known, version-specific vulnerabilities by fingerprinting the target's software stack, finding the matching CVE record, retrieving a public PoC, and adapting it to the live target. The exploit agent has four dedicated tools registered for this skill — `cve_lookup`, `cve_by_package`, `cve_by_product`, and `research_cve`. **`cve_lookup` takes CVE IDs, not a product name** — it scores\u002Franks IDs you already have (CVSS × EPSS × KEV), it does not discover them. If you load this skill, you MUST invoke `cve_lookup` and `research_cve`; `cve_by_package`\u002F`cve_by_product` are mandatory only for the matching discovery path in Step 2 (ecosystem package vs. CMS\u002Fframework core).\n\n## When to load\n\nLoad this skill (in addition to or instead of an attack-class skill) when ANY of the following hold:\n\n1. The challenge `Tags:` line contains `cve`.\n2. Recon `SUMMARY.md` fingerprinted a CMS, framework, or service with a concrete version (e.g. `WordPress 5.7.1`, `Apache Struts 2.5.16`, `Drupal 7.58`, `Spring Framework 5.3.17`, `Log4j 2.14.0`).\n3. The challenge name or description hints at specific software (`WordPress`, `Joomla`, `phpMyAdmin`, `Spring4Shell`, `Log4Shell`, `Shellshock`, `ProxyShell`, `GhostCat`, etc.).\n4. Recon returned a `RECON_HANDOFF:` line that names a software product with a version string.\n\nIf none of the above hold, do NOT load this skill — fall back to the attack-class skill matching the symptom (sqli\u002Fssti\u002Flfi\u002Fcommand-injection\u002Fetc.).\n\n## Step 1 — Fingerprinting procedure\n\nConcrete probes. Save every output to a file; do NOT inline curl bodies.\n\n```bash\n# Generic banner \u002F header \u002F generator-meta fingerprinting\ncurl -sI \"http:\u002F\u002F$TARGET\u002F\" -o \u002Ftmp\u002Fcve_headers.txt\ngrep -iE 'server|x-powered-by|x-aspnet-version|x-version|x-generator' \u002Ftmp\u002Fcve_headers.txt\n\ncurl -s \"http:\u002F\u002F$TARGET\u002F\" -o \u002Ftmp\u002Fcve_home.html\ngrep -iE 'generator|powered by|x-version|wp-includes\u002Fjs\u002Fwp-emoji|joomla|drupal|wp-content' \u002Ftmp\u002Fcve_home.html | head -20\n\n# nmap service\u002Fversion detection (when a non-HTTP port is exposed)\nnmap -sV -On -p- --version-intensity 7 \"$TARGET_HOST\" -oN \u002Ftmp\u002Fcve_nmap.txt\n\n# whatweb — broad CMS\u002Fframework signature scan\nwhatweb -a 3 \"http:\u002F\u002F$TARGET\u002F\" --no-errors > \u002Ftmp\u002Fcve_whatweb.txt 2>&1\n\n# WordPress-specific\ncurl -sI \"http:\u002F\u002F$TARGET\u002Fwp-login.php\" -o \u002Ftmp\u002Fcve_wp_login.txt\ncurl -s   \"http:\u002F\u002F$TARGET\u002Freadme.html\" -o \u002Ftmp\u002Fcve_wp_readme.html\ngrep -iE 'version' \u002Ftmp\u002Fcve_wp_readme.html | head -5\n\n# WordPress plugin enumeration (preferred: wpscan)\nwpscan --url \"http:\u002F\u002F$TARGET\u002F\" --enumerate p,t,u --no-banner --random-user-agent \\\n  -o \u002Ftmp\u002Fcve_wpscan.txt 2>&1\n\n# Manual plugin readme sweep (fallback when wpscan is unavailable)\nfor plugin in contact-form-7 woocommerce elementor yoast-seo akismet jetpack \\\n              wp-super-cache w3-total-cache wordfence all-in-one-seo-pack \\\n              wpforms-lite duplicator updraftplus classic-editor really-simple-ssl \\\n              wp-mail-smtp redirection wp-statistics polylang loginizer \\\n              simple-membership easy-wp-smtp mainwp-child seo-by-rank-math \\\n              wp-fastest-cache litespeed-cache autoptimize wp-optimize \\\n              advanced-custom-fields better-wp-security; do\n    code=$(curl -s -o \u002Fdev\u002Fnull -w '%{http_code}' \\\n        \"http:\u002F\u002F$TARGET\u002Fwp-content\u002Fplugins\u002F${plugin}\u002Freadme.txt\")\n    if [ \"$code\" = \"200\" ]; then\n        ver=$(curl -s \"http:\u002F\u002F$TARGET\u002Fwp-content\u002Fplugins\u002F${plugin}\u002Freadme.txt\" \\\n              | grep -iE 'stable tag|^version' | head -1)\n        echo \"plugin=$plugin version=$ver\"\n    fi\ndone | tee \u002Ftmp\u002Fcve_wp_plugins.txt\n\n# Joomla \u002F Drupal\ncurl -s \"http:\u002F\u002F$TARGET\u002Fadministrator\u002Fmanifests\u002Ffiles\u002Fjoomla.xml\" -o \u002Ftmp\u002Fcve_joomla.xml\ncurl -s \"http:\u002F\u002F$TARGET\u002FCHANGELOG.txt\" -o \u002Ftmp\u002Fcve_drupal_changelog.txt\n```\n\n**Output discipline**: at the end of Step 1 you MUST have at least one `\u003Csoftware>@\u003Cversion>` pair (e.g. `wordpress@5.7.1`, `contact-form-7@5.1.6`, `apache-struts@2.5.16`). If you don't, fingerprinting failed — see the Decision Tree below.\n\n## Step 2 — CVE identification: MANDATORY tool sequence\n\n`cve_lookup` does **not** search by product name — it only scores CVE IDs you already have. Discovering candidate IDs is a separate step, and which tool does it depends on what Step 1 fingerprinted:\n\n### 2a — Ecosystem package (dependency pulled in via a package manager)\n\nIf the fingerprinted component has a package-manager identity — a bundled JS\u002FPython\u002FGo\u002FJava dependency, or a WordPress\u002FJoomla plugin distributed via Composer\u002Fnpm — query OSV directly:\n\n```text\ncve_by_package(\"contact-form-7\", \"5.1.6\", ecosystem=\"Packagist\")\n# → returns: {\"package\": \"contact-form-7\", \"version\": \"5.1.6\", \"ids\": [\"CVE-xxxx-xxxxx\", \"GHSA-xxxx-xxxx-xxxx\"]}\n```\n\n`ecosystem` is one of PyPI, npm, crates.io, Go, Maven, RubyGems, NuGet, Packagist, Pub, Hex — pick the one matching how the dependency was actually installed, not a guess.\n\n### 2b — CMS\u002Fframework\u002Fruntime core (no package-manager identity)\n\nFor the product itself (WordPress core, Joomla, Apache Struts, Drupal core), use `cve_by_product` — it runs the same NVD keyword search a human analyst would, without you hand-building the query:\n\n```text\ncve_by_product(\"wordpress\", \"5.7.1\")\n# → returns: {\"product\": \"wordpress\", \"version\": \"5.7.1\",\n#             \"candidates\": [{\"cve_id\": \"CVE-xxxx-xxxxx\", \"summary\": \"...\"}, ...]}\n```\n\nResults are candidates (free-text description match, not an exact CPE\u002Fversion-range match) — skim each `summary` for version-range language (e.g. \"before 5.7.2\") before passing the ID to `cve_lookup`. If it returns no candidates, retry with just the product name (drop the version): some CVE descriptions state an affected range rather than repeating your exact version string.\n\nDo NOT fall back to a free-form web search instead of this tool — it is slower and produces stale leads.\n\n### 2c — Score every candidate ID (both paths converge here, MANDATORY)\n\nFeed every ID collected in 2a\u002F2b into `cve_lookup` to rank by real-world exploitability:\n\n```text\ncve_lookup(\"CVE-2018-11776,CVE-2017-5638\")\n# → returns: ranked list, CVSS x EPSS x KEV composite score, highest first\n```\n\nFor EACH candidate CVE returned, immediately call `research_cve` to retrieve PoC URLs (github.com\u002Ftrickest\u002Fcve, exploit-db, packetstorm, etc.):\n\n```text\nresearch_cve(\"CVE-2018-11776\")\n# → returns: github.com\u002Ftrickest\u002Fcve\u002Fblob\u002Fmain\u002F2018\u002FCVE-2018-11776.md\n#            https:\u002F\u002Fwww.exploit-db.com\u002Fexploits\u002F45260\n```\n\n**Hard rule**: if you load this skill and do NOT invoke `cve_lookup` before the first exploit attempt, you are wasting the dispatch.\n\n## Step 3 — PoC adaptation\n\nAfter `research_cve` returns URLs, fetch the PoC to disk and adapt it. Three concrete patterns:\n\n### Pattern A — curl one-shot exploit endpoint\n\nFor CVEs that are a single HTTP request (most WordPress\u002FJoomla auth-bypass and SSRF CVEs):\n\n```bash\n# Sanity-check the PoC matches the fingerprinted version BEFORE firing\ncurl -s \"https:\u002F\u002Fraw.githubusercontent.com\u002Ftrickest\u002Fcve\u002Fmain\u002F2018\u002FCVE-2018-11776.md\" \\\n  -o \u002Ftmp\u002Fcve_poc.md\ngrep -iE 'affected|version|tested on' \u002Ftmp\u002Fcve_poc.md | head -10\n# Confirm the version in the PoC overlaps the target's fingerprinted version.\n\n# Fire the adapted exploit (replace TARGET URL, OS command, output path)\ncurl -s -X POST \"http:\u002F\u002F$TARGET\u002F\u003CVULNERABLE_ENDPOINT>\" \\\n  -H 'Content-Type: application\u002Fx-www-form-urlencoded' \\\n  --data-urlencode \"\u003CPARAM>=\u003CPAYLOAD>\" \\\n  -o \u002Ftmp\u002Fcve_exploit_out.txt\nhead -50 \u002Ftmp\u002Fcve_exploit_out.txt\n```\n\n### Pattern B — python PoC script\n\nFor CVEs distributed as a Python script (Spring4Shell, Log4Shell helpers, ProxyShell):\n\n```bash\n# Fetch script to disk — never pipe untrusted code into bash directly\nwget -q \"https:\u002F\u002Fraw.githubusercontent.com\u002F\u003Cuser>\u002F\u003Crepo>\u002Fmain\u002Fpoc.py\" -O \u002Ftmp\u002Fcve_poc.py\nhead -40 \u002Ftmp\u002Fcve_poc.py    # sanity-read the script\n\n# Identify and replace placeholders (TARGET URL, CMD, callback host)\nsed -i \"s|http:\u002F\u002Ftarget|http:\u002F\u002F$TARGET|g\" \u002Ftmp\u002Fcve_poc.py\npython3 \u002Ftmp\u002Fcve_poc.py --target \"http:\u002F\u002F$TARGET\" --cmd 'id' > \u002Ftmp\u002Fcve_poc_run.txt 2>&1\nhead -50 \u002Ftmp\u002Fcve_poc_run.txt\n```\n\n### Pattern C — Metasploit module reference\n\nIf `research_cve` returns a Metasploit module name (e.g. `exploit\u002Fmulti\u002Fhttp\u002Fstruts2_content_type_ognl`), translate the module into a curl-equivalent rather than launching `msfconsole` (msfconsole is heavy and breaks the bash-output budget). Read the module's source via the module URL, extract the HTTP request it sends, and reproduce with curl. Document the module name in `exploit\u002FPIVOT.md` for traceability.\n\n**Version sanity-check is MANDATORY**: a PoC for `Struts 2.3.x` typically does NOT fire on `Struts 2.5.x`. If versions mismatch, fall back to the next CVE candidate from Step 2 rather than burning the dispatch on a guaranteed-fail attempt.\n\n## Step 4 — Post-exploit harvest\n\nOnce RCE is achieved through the CVE, load `command-injection.md` and run its \"Credential\u002FSecret Extraction After RCE Confirmed\" single-call sweep — that is the canonical generic post-RCE harvest (`\u002Fetc\u002Fpasswd`, `.env`, configs, SSH keys, secret\u002Fcred\u002Ftoken files).\n\nIf the engagement is a CTF\u002Fbenchmark (`BENCHMARK_MODE=1`), additionally load `\u002Fskills\u002Fbenchmark\u002FSKILL.md` for flag-path conventions. Generic CVE methodology never assumes CTF-specific paths.\n\n## Step 5 — Decision tree\n\n```\nCVE skill loaded?\n├── Fingerprinting yielded \u003Csoftware>@\u003Cversion>\n│   ├── Ecosystem package (npm\u002FPyPI\u002FPackagist\u002F... dependency) → cve_by_package(name, version, ecosystem)\n│   └── CMS\u002Fframework\u002Fruntime core → cve_by_product(name, version) (Step 2b) for candidate IDs\n│   ↓\n│   cve_lookup(\u003Ccomma-separated candidate IDs>)\n│   ├── >=1 CVE scored → for each (highest score first), research_cve(\u003CCVE-ID>)\n│   │   ├── PoC version matches target → adapt (Pattern A\u002FB\u002FC) and fire\n│   │   ├── PoC requires authentication → first check `default_credentials` tag,\n│   │   │    try admin\u002Fadmin, admin\u002Fpassword, root\u002Froot, then login-form recon\n│   │   └── PoC fired → on RCE, run Step 4 post-exploit harvest\n│   └── 0 candidate IDs found → check one level deeper:\n│       ├── WordPress core OK → enumerate plugins\u002Fthemes (Step 1 wpscan\u002Freadme sweep)\n│       │     then repeat Step 2 for the plugin\n│       └── Framework OK → check bundled libraries \u002F dependencies\n│             (e.g. Spring app w\u002F vulnerable log4j → cve_by_package(\"log4j-core\", \"2.14.1\", ecosystem=\"Maven\"))\n└── Fingerprinting FAILED (no version exposed)\n    ├── Pivot to attack-class probes from recon SUMMARY.md tags:\n    │     sqli.md, ssti.md, lfi.md, command-injection.md\n    └── Write exploit\u002FPIVOT.md noting \"no version banner — CVE path exhausted\"\n```\n\n## Step 6 — Pacing rule (3-strike, cross-CVE)\n\nSame payload-class 3-strike rule applies, **at the CVE level**:\n\n- If 3 candidate CVEs from `cve_lookup` all fail to exploit (version mismatch, patched endpoint, auth required without creds, or PoC returns no useful output), pivot to a DIFFERENT attack class identified during recon.\n- \"Same class\" at this skill's level = same CVE family on the same product. Three Struts RCE CVEs against the same Struts service is ONE class — after 3 strikes, pivot to sqli\u002Fssti\u002Flfi against the broader app rather than searching for a 4th Struts CVE.\n- A CVE that returns \"endpoint exists but no command output\" is a partial-strike: try Pattern B (python PoC) or out-of-band exfil (see `command-injection.md` Blind Exfiltration) before declaring strike.\n\nAfter exhausting 3 CVE candidates: the version is either patched in-place or the product surface is hardened. Write `exploit\u002FPIVOT.md` documenting (a) the 3 CVEs tried, (b) why each failed (version, auth, no-output), (c) the next attack class to attempt from recon's tag list.\n\n## Cross-skill loading\n\n- For RCE-class CVEs, after firing the exploit, load `command-injection.md` for output-extraction and blind-exfil patterns.\n- For SQLi-class CVEs (e.g. CVE-2019-7139, CVE-2020-25213), load `sqli.md` \u002F `blind-sqli.md` after the CVE confirms the injection point.\n- For LFI-class CVEs (e.g. CVE-2019-9978, CVE-2021-41773), load `lfi.md` for wrapper escalation.\n- For deserialization CVEs (Spring4Shell, ApacheCommons), load `deserialization.md` for payload generation.\n\nThe CVE skill is the **entry**; the attack-class skill is the **continuation** once the injection primitive is confirmed.\n","# CVE \u002F Known-Exploit Methodology\n\nExploits known, version-specific vulnerabilities by fingerprinting the target's software stack, finding the matching CVE record, retrieving a public PoC, and adapting it to the live target. The exploit agent has four dedicated tools registered for this skill — `cve_lookup`, `cve_by_package`, `cve_by_product`, and `research_cve`. **`cve_lookup` takes CVE IDs, not a product name** — it scores\u002Franks IDs you already have (CVSS × EPSS × KEV), it does not discover them. If you load this skill, you MUST invoke `cve_lookup` and `research_cve`; `cve_by_package`\u002F`cve_by_product` are mandatory only for the matching discovery path in Step 2 (ecosystem package vs. CMS\u002Fframework core).\n\n## When to load\n\nLoad this skill (in addition to or instead of an attack-class skill) when ANY of the following hold:\n\n1. The challenge `Tags:` line contains `cve`.\n2. Recon `SUMMARY.md` fingerprinted a CMS, framework, or service with a concrete version (e.g. `WordPress 5.7.1`, `Apache Struts 2.5.16`, `Drupal 7.58`, `Spring Framework 5.3.17`, `Log4j 2.14.0`).\n3. The challenge name or description hints at specific software (`WordPress`, `Joomla`, `phpMyAdmin`, `Spring4Shell`, `Log4Shell`, `Shellshock`, `ProxyShell`, `GhostCat`, etc.).\n4. Recon returned a `RECON_HANDOFF:` line that names a software product with a version string.\n\nIf none of the above hold, do NOT load this skill — fall back to the attack-class skill matching the symptom (sqli\u002Fssti\u002Flfi\u002Fcommand-injection\u002Fetc.).\n\n## Step 1 — Fingerprinting procedure\n\nConcrete probes. Save every output to a file; do NOT inline curl bodies.\n\n```bash\n# Generic banner \u002F header \u002F generator-meta fingerprinting\ncurl -sI \"http:\u002F\u002F$TARGET\u002F\" -o \u002Ftmp\u002Fcve_headers.txt\ngrep -iE 'server|x-powered-by|x-aspnet-version|x-version|x-generator' \u002Ftmp\u002Fcve_headers.txt\n\ncurl -s \"http:\u002F\u002F$TARGET\u002F\" -o \u002Ftmp\u002Fcve_home.html\ngrep -iE 'generator|powered by|x-version|wp-includes\u002Fjs\u002Fwp-emoji|joomla|drupal|wp-content' \u002Ftmp\u002Fcve_home.html | head -20\n\n# nmap service\u002Fversion detection (when a non-HTTP port is exposed)\nnmap -sV -On -p- --version-intensity 7 \"$TARGET_HOST\" -oN \u002Ftmp\u002Fcve_nmap.txt\n\n# whatweb — broad CMS\u002Fframework signature scan\nwhatweb -a 3 \"http:\u002F\u002F$TARGET\u002F\" --no-errors > \u002Ftmp\u002Fcve_whatweb.txt 2>&1\n\n# WordPress-specific\ncurl -sI \"http:\u002F\u002F$TARGET\u002Fwp-login.php\" -o \u002Ftmp\u002Fcve_wp_login.txt\ncurl -s   \"http:\u002F\u002F$TARGET\u002Freadme.html\" -o \u002Ftmp\u002Fcve_wp_readme.html\ngrep -iE 'version' \u002Ftmp\u002Fcve_wp_readme.html | head -5\n\n# WordPress plugin enumeration (preferred: wpscan)\nwpscan --url \"http:\u002F\u002F$TARGET\u002F\" --enumerate p,t,u --no-banner --random-user-agent \\\n  -o \u002Ftmp\u002Fcve_wpscan.txt 2>&1\n\n# Manual plugin readme sweep (fallback when wpscan is unavailable)\nfor plugin in contact-form-7 woocommerce elementor yoast-seo akismet jetpack \\\n              wp-super-cache w3-total-cache wordfence all-in-one-seo-pack \\\n              wpforms-lite duplicator updraftplus classic-editor really-simple-ssl \\\n              wp-mail-smtp redirection wp-statistics polylang loginizer \\\n              simple-membership easy-wp-smtp mainwp-child seo-by-rank-math \\\n              wp-fastest-cache litespeed-cache autoptimize wp-optimize \\\n              advanced-custom-fields better-wp-security; do\n    code=$(curl -s -o \u002Fdev\u002Fnull -w '%{http_code}' \\\n        \"http:\u002F\u002F$TARGET\u002Fwp-content\u002Fplugins\u002F${plugin}\u002Freadme.txt\")\n    if [ \"$code\" = \"200\" ]; then\n        ver=$(curl -s \"http:\u002F\u002F$TARGET\u002Fwp-content\u002Fplugins\u002F${plugin}\u002Freadme.txt\" \\\n              | grep -iE 'stable tag|^version' | head -1)\n        echo \"plugin=$plugin version=$ver\"\n    fi\ndone | tee \u002Ftmp\u002Fcve_wp_plugins.txt\n\n# Joomla \u002F Drupal\ncurl -s \"http:\u002F\u002F$TARGET\u002Fadministrator\u002Fmanifests\u002Ffiles\u002Fjoomla.xml\" -o \u002Ftmp\u002Fcve_joomla.xml\ncurl -s \"http:\u002F\u002F$TARGET\u002FCHANGELOG.txt\" -o \u002Ftmp\u002Fcve_drupal_changelog.txt\n```\n\n**Output discipline**: at the end of Step 1 you MUST have at least one `\u003Csoftware>@\u003Cversion>` pair (e.g. `wordpress@5.7.1`, `contact-form-7@5.1.6`, `apache-struts@2.5.16`). If you don't, fingerprinting failed — see the Decision Tree below.\n\n## Step 2 — CVE identification: MANDATORY tool sequence\n\n`cve_lookup` does **not** search by product name — it only scores CVE IDs you already have. Discovering candidate IDs is a separate step, and which tool does it depends on what Step 1 fingerprinted:\n\n### 2a — Ecosystem package (dependency pulled in via a package manager)\n\nIf the fingerprinted component has a package-manager identity — a bundled JS\u002FPython\u002FGo\u002FJava dependency, or a WordPress\u002FJoomla plugin distributed via Composer\u002Fnpm — query OSV directly:\n\n```text\ncve_by_package(\"contact-form-7\", \"5.1.6\", ecosystem=\"Packagist\")\n# → returns: {\"package\": \"contact-form-7\", \"version\": \"5.1.6\", \"ids\": [\"CVE-xxxx-xxxxx\", \"GHSA-xxxx-xxxx-xxxx\"]}\n```\n\n`ecosystem` is one of PyPI, npm, crates.io, Go, Maven, RubyGems, NuGet, Packagist, Pub, Hex — pick the one matching how the dependency was actually installed, not a guess.\n\n### 2b — CMS\u002Fframework\u002Fruntime core (no package-manager identity)\n\nFor the product itself (WordPress core, Joomla, Apache Struts, Drupal core), use `cve_by_product` — it runs the same NVD keyword search a human analyst would, without you hand-building the query:\n\n```text\ncve_by_product(\"wordpress\", \"5.7.1\")\n# → returns: {\"product\": \"wordpress\", \"version\": \"5.7.1\",\n#             \"candidates\": [{\"cve_id\": \"CVE-xxxx-xxxxx\", \"summary\": \"...\"}, ...]}\n```\n\nResults are candidates (free-text description match, not an exact CPE\u002Fversion-range match) — skim each `summary` for version-range language (e.g. \"before 5.7.2\") before passing the ID to `cve_lookup`. If it returns no candidates, retry with just the product name (drop the version): some CVE descriptions state an affected range rather than repeating your exact version string.\n\nDo NOT fall back to a free-form web search instead of this tool — it is slower and produces stale leads.\n\n### 2c — Score every candidate ID (both paths converge here, MANDATORY)\n\nFeed every ID collected in 2a\u002F2b into `cve_lookup` to rank by real-world exploitability:\n\n```text\ncve_lookup(\"CVE-2018-11776,CVE-2017-5638\")\n# → returns: ranked list, CVSS x EPSS x KEV composite score, highest first\n```\n\nFor EACH candidate CVE returned, immediately call `research_cve` to retrieve PoC URLs (github.com\u002Ftrickest\u002Fcve, exploit-db, packetstorm, etc.):\n\n```text\nresearch_cve(\"CVE-2018-11776\")\n# → returns: github.com\u002Ftrickest\u002Fcve\u002Fblob\u002Fmain\u002F2018\u002FCVE-2018-11776.md\n#            https:\u002F\u002Fwww.exploit-db.com\u002Fexploits\u002F45260\n```\n\n**Hard rule**: if you load this skill and do NOT invoke `cve_lookup` before the first exploit attempt, you are wasting the dispatch.\n\n## Step 3 — PoC adaptation\n\nAfter `research_cve` returns URLs, fetch the PoC to disk and adapt it. Three concrete patterns:\n\n### Pattern A — curl one-shot exploit endpoint\n\nFor CVEs that are a single HTTP request (most WordPress\u002FJoomla auth-bypass and SSRF CVEs):\n\n```bash\n# Sanity-check the PoC matches the fingerprinted version BEFORE firing\ncurl -s \"https:\u002F\u002Fraw.githubusercontent.com\u002Ftrickest\u002Fcve\u002Fmain\u002F2018\u002FCVE-2018-11776.md\" \\\n  -o \u002Ftmp\u002Fcve_poc.md\ngrep -iE 'affected|version|tested on' \u002Ftmp\u002Fcve_poc.md | head -10\n# Confirm the version in the PoC overlaps the target's fingerprinted version.\n\n# Fire the adapted exploit (replace TARGET URL, OS command, output path)\ncurl -s -X POST \"http:\u002F\u002F$TARGET\u002F\u003CVULNERABLE_ENDPOINT>\" \\\n  -H 'Content-Type: application\u002Fx-www-form-urlencoded' \\\n  --data-urlencode \"\u003CPARAM>=\u003CPAYLOAD>\" \\\n  -o \u002Ftmp\u002Fcve_exploit_out.txt\nhead -50 \u002Ftmp\u002Fcve_exploit_out.txt\n```\n\n### Pattern B — python PoC script\n\nFor CVEs distributed as a Python script (Spring4Shell, Log4Shell helpers, ProxyShell):\n\n```bash\n# Fetch script to disk — never pipe untrusted code into bash directly\nwget -q \"https:\u002F\u002Fraw.githubusercontent.com\u002F\u003Cuser>\u002F\u003Crepo>\u002Fmain\u002Fpoc.py\" -O \u002Ftmp\u002Fcve_poc.py\nhead -40 \u002Ftmp\u002Fcve_poc.py    # sanity-read the script\n\n# Identify and replace placeholders (TARGET URL, CMD, callback host)\nsed -i \"s|http:\u002F\u002Ftarget|http:\u002F\u002F$TARGET|g\" \u002Ftmp\u002Fcve_poc.py\npython3 \u002Ftmp\u002Fcve_poc.py --target \"http:\u002F\u002F$TARGET\" --cmd 'id' > \u002Ftmp\u002Fcve_poc_run.txt 2>&1\nhead -50 \u002Ftmp\u002Fcve_poc_run.txt\n```\n\n### Pattern C — Metasploit module reference\n\nIf `research_cve` returns a Metasploit module name (e.g. `exploit\u002Fmulti\u002Fhttp\u002Fstruts2_content_type_ognl`), translate the module into a curl-equivalent rather than launching `msfconsole` (msfconsole is heavy and breaks the bash-output budget). Read the module's source via the module URL, extract the HTTP request it sends, and reproduce with curl. Document the module name in `exploit\u002FPIVOT.md` for traceability.\n\n**Version sanity-check is MANDATORY**: a PoC for `Struts 2.3.x` typically does NOT fire on `Struts 2.5.x`. If versions mismatch, fall back to the next CVE candidate from Step 2 rather than burning the dispatch on a guaranteed-fail attempt.\n\n## Step 4 — Post-exploit harvest\n\nOnce RCE is achieved through the CVE, load `command-injection.md` and run its \"Credential\u002FSecret Extraction After RCE Confirmed\" single-call sweep — that is the canonical generic post-RCE harvest (`\u002Fetc\u002Fpasswd`, `.env`, configs, SSH keys, secret\u002Fcred\u002Ftoken files).\n\nIf the engagement is a CTF\u002Fbenchmark (`BENCHMARK_MODE=1`), additionally load `\u002Fskills\u002Fbenchmark\u002FSKILL.md` for flag-path conventions. Generic CVE methodology never assumes CTF-specific paths.\n\n## Step 5 — Decision tree\n\n```\nCVE skill loaded?\n├── Fingerprinting yielded \u003Csoftware>@\u003Cversion>\n│   ├── Ecosystem package (npm\u002FPyPI\u002FPackagist\u002F... dependency) → cve_by_package(name, version, ecosystem)\n│   └── CMS\u002Fframework\u002Fruntime core → cve_by_product(name, version) (Step 2b) for candidate IDs\n│   ↓\n│   cve_lookup(\u003Ccomma-separated candidate IDs>)\n│   ├── >=1 CVE scored → for each (highest score first), research_cve(\u003CCVE-ID>)\n│   │   ├── PoC version matches target → adapt (Pattern A\u002FB\u002FC) and fire\n│   │   ├── PoC requires authentication → first check `default_credentials` tag,\n│   │   │    try admin\u002Fadmin, admin\u002Fpassword, root\u002Froot, then login-form recon\n│   │   └── PoC fired → on RCE, run Step 4 post-exploit harvest\n│   └── 0 candidate IDs found → check one level deeper:\n│       ├── WordPress core OK → enumerate plugins\u002Fthemes (Step 1 wpscan\u002Freadme sweep)\n│       │     then repeat Step 2 for the plugin\n│       └── Framework OK → check bundled libraries \u002F dependencies\n│             (e.g. Spring app w\u002F vulnerable log4j → cve_by_package(\"log4j-core\", \"2.14.1\", ecosystem=\"Maven\"))\n└── Fingerprinting FAILED (no version exposed)\n    ├── Pivot to attack-class probes from recon SUMMARY.md tags:\n    │     sqli.md, ssti.md, lfi.md, command-injection.md\n    └── Write exploit\u002FPIVOT.md noting \"no version banner — CVE path exhausted\"\n```\n\n## Step 6 — Pacing rule (3-strike, cross-CVE)\n\nSame payload-class 3-strike rule applies, **at the CVE level**:\n\n- If 3 candidate CVEs from `cve_lookup` all fail to exploit (version mismatch, patched endpoint, auth required without creds, or PoC returns no useful output), pivot to a DIFFERENT attack class identified during recon.\n- \"Same class\" at this skill's level = same CVE family on the same product. Three Struts RCE CVEs against the same Struts service is ONE class — after 3 strikes, pivot to sqli\u002Fssti\u002Flfi against the broader app rather than searching for a 4th Struts CVE.\n- A CVE that returns \"endpoint exists but no command output\" is a partial-strike: try Pattern B (python PoC) or out-of-band exfil (see `command-injection.md` Blind Exfiltration) before declaring strike.\n\nAfter exhausting 3 CVE candidates: the version is either patched in-place or the product surface is hardened. Write `exploit\u002FPIVOT.md` documenting (a) the 3 CVEs tried, (b) why each failed (version, auth, no-output), (c) the next attack class to attempt from recon's tag list.\n\n## Cross-skill loading\n\n- For RCE-class CVEs, after firing the exploit, load `command-injection.md` for output-extraction and blind-exfil patterns.\n- For SQLi-class CVEs (e.g. CVE-2019-7139, CVE-2020-25213), load `sqli.md` \u002F `blind-sqli.md` after the CVE confirms the injection point.\n- For LFI-class CVEs (e.g. CVE-2019-9978, CVE-2021-41773), load `lfi.md` for wrapper escalation.\n- For deserialization CVEs (Spring4Shell, ApacheCommons), load `deserialization.md` for payload generation.\n\nThe CVE skill is the **entry**; the attack-class skill is the **continuation** once the injection primitive is confirmed.\n",{"name":5,"metadata":24,"description":7,"allowed-tools":29},{"tags":25,"subdomain":26,"when_to_use":27,"mitre_attack":28},"web-application, cve, known-exploit, n-day, public-poc","execution","cve, CVE, known vulnerability, public exploit, version-specific, plugin vulnerability, CMS exploit, WordPress vulnerability, vulnerable software, patched, unpatched, joomla vulnerability, drupal vulnerability, apache struts, spring4shell, log4j, log4shell, exploit-db, public PoC, n-day exploit, cve_lookup, cve_by_package, cve_by_product, research_cve","T1190, T1203, T1059","Bash Read Write","master","8e5d356b795eae2edd4a26509a4b8968e2c4c251","packages\u002Fraptix-skills\u002Fraptix_skills\u002Fdefs\u002Fstandard\u002Fexploit\u002Fweb\u002Fcve","https:\u002F\u002Fgithub.com\u002FAkapi895\u002Fraptix","https:\u002F\u002Fgithub.com\u002FAkapi895","2026-11-06 17:46:09",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add Akapi895\u002Fraptix --skill cve",{"tool":42,"command":43},"bunx","bunx skills add Akapi895\u002Fraptix --skill cve",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Akapi895\u002Fraptix --skill cve","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAkapi895\u002Fraptix\u002Fblob\u002Fmaster\u002Fpackages\u002Fraptix-skills\u002Fraptix_skills\u002Fdefs\u002Fstandard\u002Fexploit\u002Fweb\u002Fcve\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7DGM32SRP4FZSPYWY621BKQ","wps-pixie-dust","WPS Pixie-Dust offline nonce attack (reaver -K \u002F pixiewps) and fallback online PIN brute (bully) to recover the AP's WPA PSK without capturing a handshake.","https:\u002F\u002Fgithub.com\u002FAkapi895\u002Fraptix\u002Fblob\u002Fmaster\u002Fpackages\u002Fraptix-skills\u002Fraptix_skills\u002Fdefs\u002Fstandard\u002Fwireless\u002Fwps-pixie-dust\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7DGKXXVDTY0KBZZR83VFPZX","wpa3-sae","WPA3-SAE transition-mode downgrade (DragonShift), SSID Confusion CVE-2023-52424, Dragonblood side-channels, and SAE captive-portal credential recovery against WPA3-Personal networks.","https:\u002F\u002Fgithub.com\u002FAkapi895\u002Fraptix\u002Fblob\u002Fmaster\u002Fpackages\u002Fraptix-skills\u002Fraptix_skills\u002Fdefs\u002Fstandard\u002Fwireless\u002Fwpa3-sae\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7DGKSV77ENX3D6TG2HQX9MK","wpa2-psk","WPA\u002FWPA2-PSK handshake capture via targeted deauth + PMKID (no deauth required) + offline hashcat cracking. The most common consumer\u002FSMB encryption mode in 2026.","https:\u002F\u002Fgithub.com\u002FAkapi895\u002Fraptix\u002Fblob\u002Fmaster\u002Fpackages\u002Fraptix-skills\u002Fraptix_skills\u002Fdefs\u002Fstandard\u002Fwireless\u002Fwpa2-psk\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7DGKJ9R6YTFRFBSEAJRGGKF","wpa-enterprise-eap","WPA\u002FWPA2\u002FWPA3-Enterprise (802.1X\u002FEAP) rogue-RADIUS evil-twin for MSCHAPv2 capture, GTC downgrade, and PEAP relay. MSCHAPv2 capture equals a NetNTLM hash — the primary wireless on-ramp to Active Directory.","https:\u002F\u002Fgithub.com\u002FAkapi895\u002Fraptix\u002Fblob\u002Fmaster\u002Fpackages\u002Fraptix-skills\u002Fraptix_skills\u002Fdefs\u002Fstandard\u002Fwireless\u002Fwpa-enterprise-eap\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7DGKCFZGKK2EQMWZM1A18S8","krack-fragattacks","KRACK key-reinstallation (CVE-2017-13077..13082) and FragAttacks fragmentation\u002Faggregation flaws (CVE-2020-24586..24588, CVE-2020-26139..26147) against legacy or embedded 802.11 supplicants with poor patch cadence.","https:\u002F\u002Fgithub.com\u002FAkapi895\u002Fraptix\u002Fblob\u002Fmaster\u002Fpackages\u002Fraptix-skills\u002Fraptix_skills\u002Fdefs\u002Fstandard\u002Fwireless\u002Fkrack-fragattacks\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7DGK76MKZQWBXTZN82W7214","evil-twin-karma","Evil-twin rogue AP with KARMA\u002FMana PNL-probe response, captive-portal credential capture, and post-association MITM for PSK\u002Fopen networks. Distinct from wpa-enterprise-eap which targets 802.1X.","https:\u002F\u002Fgithub.com\u002FAkapi895\u002Fraptix\u002Fblob\u002Fmaster\u002Fpackages\u002Fraptix-skills\u002Fraptix_skills\u002Fdefs\u002Fstandard\u002Fwireless\u002Fevil-twin-karma\u002FSKILL.md",[],[]]