Individual skill
exploiting-sql-injection-with-sqlmap
Detecting and exploiting SQL injection vulnerabilities using sqlmap to extract database contents during authorized penetration tests.
internal/tools/skills/data/web-application-security/exploiting-sql-injection-with-sqlmap/SKILL.md
Source commit d42f381ad34843e71a42658e5c57290c713e85af
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,313
- Repository last updated
- Nov 8, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- cybersecurity Repository topic
- security Repository topic
- bug-bounty Repository topic
- automation Repository topic
- autonomous-pentesting Repository topic
- ai-agent Repository topic
- ai-security Repository topic
- ethical-hacking Repository topic
- golang Repository topic
- penetration-testing Repository topic
- penetration-testing Declared skill tag
- sql-injection Declared skill tag
- sqlmap Declared skill tag
- owasp Declared skill tag
- database-security Declared skill tag
- web-security Declared skill tag
- data Derived category
- security Derived category
- testing Derived category
- data-databases Derived category
- security-application Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Exploiting SQL Injection with sqlmap
## When to Use
- During authorized web application penetration testing engagements
- When manual testing reveals potential SQL injection points in parameters, headers, or cookies
- For validating SQL injection findings from automated scanners like Burp Suite or OWASP ZAP
- When you need to demonstrate the impact of SQL injection by extracting data from backend databases
- During CTF challenges involving SQL injection exploitation
### How to CONFIRM a Hit (avoid false negatives)
- The positive signal is sqlmap's **own technique confirmation** plus manual re-verification — not an HTTP 200. Require sqlmap to print `the parameter '<x>' is vulnerable` and list the confirmed techniques (B=boolean, E=error, U=union, S=stacked, T=time) and the back-end DBMS. A scan that ends with "all tested parameters do not appear to be injectable" is a negative ONLY after the escalations below.
- Re-verify manually so you are not chasing a false positive: reproduce the boolean differential (true vs false page differ), the time delay (a `SLEEP(5)`/`WAITFOR` payload adds ~5s vs baseline), the DB error string, or the UNION row appearing in the response. If you cannot reproduce by hand, treat sqlmap's claim with suspicion.
- Watch for false negatives from defaults: bump `--level=5 --risk=3`, set the right `--dbms`, and supply a `--technique` if only blind is viable.