timsonner Searchsploit
Purpose
Use this skill to research public exploit references after product, version, or CVE context is already confirmed.
Phase Fit
- Primary: Threat Modeling and Test Planning, Vulnerability Analysis
- Secondary: Validation and Controlled Impact Demonstration
Use When
- Need to determine whether an observed version or CVE has public exploit references.
- Need to assess attacker realism before choosing a validation path.
- Need supporting context for severity and remediation prioritization.
Avoid When
- Product or version details are unconfirmed.
- The next step would be to run exploit code without explicit approval.
Inputs
- Confirmed product name, version, banner, or CVE
- Current phase objective and allowed validation depth
Procedure
- Search by exact product or CVE first.
- Compare references to the observed environment before treating them as relevant.
- Use exploit references to guide risk discussion, not to skip validation.
- Record applicability notes and preconditions.
- Escalate to controlled validation only if the rules of engagement permit it.
Command Syntax
Use confirmed product or CVE data from the current engagement.
# Search by product and version
searchsploit apache 2.4
# Search for Windows SMB exploits
searchsploit windows smb 2017
# Search by CVE number
searchsploit --cve 2024-12345
# Case-insensitive keyword search
searchsploit -i iis 7.5
# Show full path to the exploit file
searchsploit -p 39161
# Copy exploit to current directory for modification
searchsploit -m 39161
# Update the local database
searchsploit -u
# Filter by exploit type (webapps, dos, local, remote)
searchsploit --type webapps joomla
Evidence to Capture
- Matching exploit references tied to the confirmed asset
- Applicability notes and preconditions
- Why a reference is or is not relevant to the environment
Safety Boundaries
- Do not execute public exploit code without explicit written approval.
- Treat exploit references as research inputs, not proof of exposure.