Back to catalog
Static reviewDevelopment

Skill dossier

performing-second-order-sql-injection

Source declaration

Detect and exploit second-order SQL injection vulnerabilities where malicious input is stored in a database and later executed in an unsafe SQL query during a different application operation.

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

Detect and exploit second-order SQL injection vulnerabilities where malicious input is stored in a database and later executed in an unsafe SQL query during a different application operation.

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.

Detect and exploit second-order SQL injection vulnerabilities where malicious input is stored in a database and later executed in an unsafe SQL query during a different application operation. 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/performing-second-order-sql-injection/SKILL.md:L49]
  • Step 1 — Identify Storage and Trigger Points [Source statement; provisional, not tested. Evidence: skills/performing-second-order-sql-injection/SKILL.md:L51]
  • Step 2 — Inject Payloads via Storage Points [Source statement; provisional, not tested. Evidence: skills/performing-second-order-sql-injection/SKILL.md:L73]
  • Step 3 — Trigger Execution of Stored Payloads [Source statement; provisional, not tested. Evidence: skills/performing-second-order-sql-injection/SKILL.md:L95]
  • Step 4 — Use SQLMap for Second-Order Injection [Source statement; provisional, not tested. Evidence: skills/performing-second-order-sql-injection/SKILL.md:L115]
  • Step 5 — Blind Second-Order Extraction [Source statement; provisional, not tested. Evidence: skills/performing-second-order-sql-injection/SKILL.md:L138]
  • Step 6 — Escalate to Full Database Compromise [Source statement; provisional, not tested. Evidence: skills/performing-second-order-sql-injection/SKILL.md:L162]

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/performing-second-order-sql-injection/SKILL.md:L1-L30]

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
29 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/performing-second-order-sql-injection/LICENSEOther11 KB
skills/performing-second-order-sql-injection/references/api-reference.mdReference2.6 KB
skills/performing-second-order-sql-injection/scripts/agent.pyScript6.4 KB
skills/performing-second-order-sql-injection/SKILL.mdInstruction8.9 KB

SKILL.md frontmatter

{
  "name": "performing-second-order-sql-injection",
  "description": "Detect and exploit second-order SQL injection vulnerabilities where malicious input is stored in a database and later executed in an unsafe SQL query during a different application operation.",
  "domain": "cybersecurity",
  "subdomain": "web-application-security",
  "tags": [
    "second-order-sqli",
    "stored-sql-injection",
    "sql-injection",
    "database-security",
    "web-security",
    "blind-injection",
    "persistent-sqli"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.PS-01",
    "ID.RA-01",
    "PR.DS-10",
    "DE.CM-01"
  ],
  "mitre_attack": [
    "T1190",
    "T1059.007",
    "T1505.003",
    "T1083",
    "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 — Identify Storage and Trigger Points

    Source-described action candidate under “Step 1 — Identify Storage and Trigger Points”; not verified execution.

  4. 04
    Action

    Step 2 — Inject Payloads via Storage Points

    Source-described action candidate under “Step 2 — Inject Payloads via Storage Points”; not verified execution.

  5. 05
    Action

    Step 3 — Trigger Execution of Stored Payloads

    Source-described action candidate under “Step 3 — Trigger Execution of Stored Payloads”; not verified execution.

  6. 06
    Action

    Step 4 — Use SQLMap for Second-Order Injection

    Source-described action candidate under “Step 4 — Use SQLMap for Second-Order Injection”; not verified execution.

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

    Step 5 — Blind Second-Order Extraction

    Source-described action candidate under “Step 5 — Blind Second-Order Extraction”; not verified execution.

  2. 08
    Action

    Step 6 — Escalate to Full Database Compromise

    Source-described action candidate under “Step 6 — Escalate to Full Database Compromise”; not verified execution.

  3. 09
    Action

    Key Concepts

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

  4. 10
    Action

    Tools & Systems

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

  5. 11
    Action

    Common Scenarios

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

  6. 12
    Action

    Username-Based Attack — Register with a SQL injection payload as username; the payload executes when an admin views the user list

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

  7. 13
    Action

    Password Change Exploitation — Store injection in username; when changing password, the application uses the stored username in an unsafe UPDATE query

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

  8. 14
    Output

    Report Generation Attack — Inject payload in stored data fields; triggering report generation uses stored data in aggregate queries

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

  9. 15
    Action

    Cross-User Injection — Inject payload in a shared data field (comments, reviews) that triggers when another user or admin processes the data

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

  10. 16
    Output

    Export Function Exploit — Inject payload in profile data that triggers during CSV/PDF export operations

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

  11. 17
    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

31 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

23 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 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.

Note

File modification is described or implemented

4 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 4 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

4 occurrences

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 4 location(s) in the collected text; 3 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/performing-second-order-sql-injection/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/performing-second-order-sql-injection/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/performing-second-order-sql-injection
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.