Back to catalog
Static reviewDevelopment

Skill dossier

exploiting-sql-injection-vulnerabilities

Source declaration

Identifies and exploits SQL injection vulnerabilities in web applications during authorized penetration tests using manual techniques and automated tools like sqlmap. The tester detects injection points through error-based, union-based, blind boolean, and time-based blind techniques across all major database engines (MySQL, PostgreSQL, MSSQL, Oracle) to demonstrate data extraction, authentication bypass, and potential remote code execution. Activates for requests involving SQL injection testing, SQLi exploitation, database security assessment, or injection vulnerability verification.

The author's original description, preserved in English. It describes intent, not verified performance.

Identifies and exploits SQL injection vulnerabilities in web applications during authorized penetration tests using manual techniques and automated tools like sqlmap. The tester detects injection points through error-based, union-based, blind boolean, and time-based blind techniques across all major database engines (MySQL, PostgreSQL, MSSQL, Oracle) to demonstrate data extraction, authentication bypass, and potential remote code execution. Activates for requests involving SQL injection testing, SQLi exploitation, database security assessment, or injection vulnerability verification.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Identifies and exploits SQL injection vulnerabilities in web applications during authorized penetration tests using manual techniques and automated tools like sqlmap. The tester detects injection points through error-based, union-based, blind boolean, and time-based blind techniques across all major database engines (MySQL, PostgreSQL, MSSQL, Oracle) to demonstrate data extraction, authentication bypass, and potential remote code execution. Activates for requests involving SQL injection testing, SQLi exploitation, database security assessment, or injection vulnerability verification. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/exploiting-sql-injection-vulnerabilities/SKILL.md:L56]
  • Step 1: Injection Point Discovery [Source statement; provisional, not tested. Evidence: skills/exploiting-sql-injection-vulnerabilities/SKILL.md:L58]
  • Step 2: Database Fingerprinting [Source statement; provisional, not tested. Evidence: skills/exploiting-sql-injection-vulnerabilities/SKILL.md:L69]
  • Step 3: Manual Exploitation Techniques [Source statement; provisional, not tested. Evidence: skills/exploiting-sql-injection-vulnerabilities/SKILL.md:L82]
  • Step 4: Automated Exploitation with sqlmap [Source statement; provisional, not tested. Evidence: skills/exploiting-sql-injection-vulnerabilities/SKILL.md:L107]
  • Step 5: Impact Demonstration and Reporting [Source statement; provisional, not tested. Evidence: skills/exploiting-sql-injection-vulnerabilities/SKILL.md:L120]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/exploiting-sql-injection-vulnerabilities/SKILL.md:L1-L35]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
32.6 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/exploiting-sql-injection-vulnerabilities/LICENSEOther11 KB
skills/exploiting-sql-injection-vulnerabilities/references/api-reference.mdReference1.9 KB
skills/exploiting-sql-injection-vulnerabilities/scripts/agent.pyScript7.3 KB
skills/exploiting-sql-injection-vulnerabilities/SKILL.mdInstruction12.4 KB

SKILL.md frontmatter

{
  "name": "exploiting-sql-injection-vulnerabilities",
  "description": "Identifies and exploits SQL injection vulnerabilities in web applications during authorized penetration tests using manual techniques and automated tools like sqlmap. The tester detects injection points through error-based, union-based, blind boolean, and time-based blind techniques across all major database engines (MySQL, PostgreSQL, MSSQL, Oracle) to demonstrate data extraction, authentication bypass, and potential remote code execution. Activates for requests involving SQL injection testing, SQLi exploitation, database security assessment, or injection vulnerability verification.\n",
  "domain": "cybersecurity",
  "subdomain": "penetration-testing",
  "tags": [
    "SQL-injection",
    "sqlmap",
    "database-security",
    "OWASP-A03",
    "injection-testing"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "ID.RA-01",
    "ID.RA-06",
    "GV.OV-02",
    "DE.AE-07"
  ],
  "mitre_attack": [
    "T1595",
    "T1190",
    "T1059",
    "T1078",
    "T1055"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Injection Point Discovery

    Source-described action candidate under “Step 1: Injection Point Discovery”; not verified execution.

  4. 04
    Input

    Map all input vectors: Catalog every parameter in URLs (GET), request bodies (POST), HTTP headers (Cookie, Referer, User-Agent, X-Forwarded-For), and JSON/XML API payloads

    Source-described input candidate under “Step 1: Injection Point Discovery”; not verified execution.

  5. 05
    Action

    Error-based detection: Inject a single quote (`'`) into each parameter and observe the response. SQL errors (e.g., "You have an error in your SQL syntax", "unterminated quoted string", "ORA-01756") confirm the parameter reaches the database unsanitized.

    Source-described action candidate under “Step 1: Injection Point Discovery”; not verified execution.

  6. 06
    Decision

    Boolean-based detection: Inject `' AND 1=1--` (true condition) and `' AND 1=2--` (false condition). If the responses differ (different content length, different data returned, different HTTP status), the parameter is injectable.

    Source-described decision candidate under “Step 1: Injection Point Discovery”; not verified execution.

Inspect all extracted workflow candidates (51 candidate steps)
  1. 07
    Action

    Time-based detection: Inject `'; WAITFOR DELAY '0:0:5'--` (MSSQL), `' AND SLEEP(5)--` (MySQL), or `'; SELECT pgsleep(5)--` (PostgreSQL). A 5-second response delay confirms injection.

    Source-described action candidate under “Step 1: Injection Point Discovery”; not verified execution.

  2. 08
    Action

    Out-of-band detection: Use payloads that trigger DNS or HTTP requests to a Burp Collaborator domain to confirm injection in scenarios where responses are not directly observable.

    Source-described action candidate under “Step 1: Injection Point Discovery”; not verified execution.

  3. 09
    Input

    Second-order injection: Test for injection where input is stored and later used in a different SQL query (e.g., username stored at registration, used in a query on the profile page).

    Source-described input candidate under “Step 1: Injection Point Discovery”; not verified execution.

  4. 10
    Action

    Step 2: Database Fingerprinting

    Source-described action candidate under “Step 2: Database Fingerprinting”; not verified execution.

  5. 11
    Action

    Error-based fingerprinting: Each database produces distinctive error messages. MySQL includes "MySQL", MSSQL mentions "SQL Server", PostgreSQL references "PG", Oracle contains "ORA-".

    Source-described action candidate under “Step 2: Database Fingerprinting”; not verified execution.

  6. 12
    Action

    Function-based fingerprinting: Inject database-specific functions:

    Source-described action candidate under “Step 2: Database Fingerprinting”; not verified execution.

  7. 13
    Action

    MySQL: `' AND VERSION()--` or `' AND @@version--`

    Source-described action candidate under “Step 2: Database Fingerprinting”; not verified execution.

  8. 14
    Action

    MSSQL: `' AND @@version--` or `' AND DBNAME()--`

    Source-described action candidate under “Step 2: Database Fingerprinting”; not verified execution.

  9. 15
    Action

    PostgreSQL: `' AND version()--`

    Source-described action candidate under “Step 2: Database Fingerprinting”; not verified execution.

  10. 16
    Action

    Oracle: `' AND banner FROM v$version--`

    Source-described action candidate under “Step 2: Database Fingerprinting”; not verified execution.

  11. 17
    Action

    String concatenation differences: MySQL uses `CONCAT('a','b')` or `'a' 'b'`, MSSQL uses `'a'+'b'`, PostgreSQL uses `'a'||'b'`, Oracle uses `'a'||'b'`

    Source-described action candidate under “Step 2: Database Fingerprinting”; not verified execution.

  12. 18
    Action

    Comment syntax: MySQL supports `#` and `-- `, MSSQL uses `-- `, PostgreSQL uses `-- `, Oracle uses `-- `

    Source-described action candidate under “Step 2: Database Fingerprinting”; not verified execution.

  13. 19
    Action

    Step 3: Manual Exploitation Techniques

    Source-described action candidate under “Step 3: Manual Exploitation Techniques”; not verified execution.

  14. 20
    Action

    UNION-based extraction: Determine the number of columns with `ORDER BY` incrementing (`' ORDER BY 1--`, `' ORDER BY 2--`, etc. until an error occurs). Then construct UNION SELECT to extract data:

    Source-described action candidate under “Step 3: Manual Exploitation Techniques”; not verified execution.

  15. 21
    Action

    Error-based extraction (MySQL): Use `EXTRACTVALUE` or `UPDATEXML` to force data into error messages:

    Source-described action candidate under “Step 3: Manual Exploitation Techniques”; not verified execution.

  16. 22
    Action

    Blind boolean extraction: Extract data one character at a time by testing character values:

    Source-described action candidate under “Step 3: Manual Exploitation Techniques”; not verified execution.

  17. 23
    Action

    Time-based blind extraction: Same character-by-character approach using time delays:

    Source-described action candidate under “Step 3: Manual Exploitation Techniques”; not verified execution.

  18. 24
    Action

    Stacked queries (where supported): Execute additional SQL statements:

    Source-described action candidate under “Step 3: Manual Exploitation Techniques”; not verified execution.

  19. 25
    Action

    Step 4: Automated Exploitation with sqlmap

    Source-described action candidate under “Step 4: Automated Exploitation with sqlmap”; not verified execution.

  20. 26
    Action

    Use sqlmap for efficient exploitation of confirmed injection points:

    Source-described action candidate under “Step 4: Automated Exploitation with sqlmap”; not verified execution.

  21. 27
    Action

    Basic detection: `sqlmap -u "https://target.com/page?id=1" --batch --random-agent` to detect injection and identify the database

    Source-described action candidate under “Step 4: Automated Exploitation with sqlmap”; not verified execution.

  22. 28
    Action

    Extract databases: `sqlmap -u "https://target.com/page?id=1" --dbs` to list all databases

    Source-described action candidate under “Step 4: Automated Exploitation with sqlmap”; not verified execution.

  23. 29
    Action

    Extract tables: `sqlmap -u "https://target.com/page?id=1" -D <database> --tables` to list tables

    Source-described action candidate under “Step 4: Automated Exploitation with sqlmap”; not verified execution.

  24. 30
    Action

    Extract data: `sqlmap -u "https://target.com/page?id=1" -D <database> -T users --dump --threads 5` to extract table contents

    Source-described action candidate under “Step 4: Automated Exploitation with sqlmap”; not verified execution.

  25. 31
    Action

    POST parameters: `sqlmap -u "https://target.com/login" --data="username=test&password=test" -p username` to test POST parameters

    Source-described action candidate under “Step 4: Automated Exploitation with sqlmap”; not verified execution.

  26. 32
    Action

    Cookie injection: `sqlmap -u "https://target.com/page" --cookie="session=abc123; id=1" --level 2` to test cookie parameters (mark injectable parameter with )

    Source-described action candidate under “Step 4: Automated Exploitation with sqlmap”; not verified execution.

  27. 33
    Decision

    OS command execution (if DB user has sufficient privileges): `sqlmap -u "https://target.com/page?id=1" --os-shell` to attempt command execution via xpcmdshell (MSSQL) or INTO OUTFILE (MySQL)

    Source-described decision candidate under “Step 4: Automated Exploitation with sqlmap”; not verified execution.

  28. 34
    Action

    Tamper scripts: `sqlmap -u "https://target.com/page?id=1" --tamper=space2comment,between` to bypass WAF filters

    Source-described action candidate under “Step 4: Automated Exploitation with sqlmap”; not verified execution.

  29. 35
    Action

    Step 5: Impact Demonstration and Reporting

    Source-described action candidate under “Step 5: Impact Demonstration and Reporting”; not verified execution.

  30. 36
    Output

    Data extraction evidence: Capture screenshots or sqlmap output showing extracted database names, table schemas, and sample records (redact actual PII in the report)

    Source-described output candidate under “Step 5: Impact Demonstration and Reporting”; not verified execution.

  31. 37
    Action

    Authentication bypass: Demonstrate login bypass with `admin' OR 1=1--` and document the bypassed authentication mechanism

    Source-described action candidate under “Step 5: Impact Demonstration and Reporting”; not verified execution.

  32. 38
    Decision

    Privilege escalation: If the database user has DBA privileges, document what additional capabilities are available (file read/write, command execution)

    Source-described decision candidate under “Step 5: Impact Demonstration and Reporting”; not verified execution.

  33. 39
    Decision

    Lateral movement potential: Document if the database server has network access to other internal systems that could be reached through OS-level access gained via SQLi

    Source-described decision candidate under “Step 5: Impact Demonstration and Reporting”; not verified execution.

  34. 40
    Input

    Remediation: Provide specific code-level fixes showing the vulnerable query and the corrected parameterized version

    Source-described input candidate under “Step 5: Impact Demonstration and Reporting”; not verified execution.

  35. 41
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  36. 42
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  37. 43
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  38. 44
    Action

    Map all parameters in the patient portal; identify that the appointment detail page uses `/appointment?id=4521`

    Source-described action candidate under “Scenario: SQL Injection in Healthcare Patient Portal”; not verified execution.

  39. 45
    Input

    Inject a single quote into the id parameter; receive a MySQL error confirming the parameter is injectable

    Source-described input candidate under “Scenario: SQL Injection in Healthcare Patient Portal”; not verified execution.

  40. 46
    Action

    Use `ORDER BY` to determine the query returns 7 columns

    Source-described action candidate under “Scenario: SQL Injection in Healthcare Patient Portal”; not verified execution.

  41. 47
    Action

    Construct UNION SELECT to extract table names from informationschema, discovering tables: patients, medicalrecords, billing, adminusers

    Source-described action candidate under “Scenario: SQL Injection in Healthcare Patient Portal”; not verified execution.

  42. 48
    Action

    Extract adminusers table to reveal 5 administrator accounts with MD5-hashed passwords

    Source-described action candidate under “Scenario: SQL Injection in Healthcare Patient Portal”; not verified execution.

  43. 49
    Action

    Demonstrate that patient medical records for all patients are accessible by querying the medicalrecords table through the injection point

    Source-described action candidate under “Scenario: SQL Injection in Healthcare Patient Portal”; not verified execution.

  44. 50
    Action

    Document that 15,000+ patient records containing PHI (protected health information) are accessible, constituting a HIPAA violation

    Source-described action candidate under “Scenario: SQL Injection in Healthcare Patient Portal”; not verified execution.

  45. 51
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

38 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

14 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 14 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

23 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 23 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/exploiting-sql-injection-vulnerabilities/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/exploiting-sql-injection-vulnerabilities/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/exploiting-sql-injection-vulnerabilities
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.