Skills webapp-sqlmap

📦

webapp-sqlmap

Name: webapp-sqlmap
Author: AgentSecOps

v0.1.0 Content revision r2 Critical ⚙️ External commands🌐 Network access📁 Filesystem access🔑 Env variables⚡ Contains scripts

Assess SQL Injection with SQLMap

Manual SQL injection testing is slow and inconsistent. This skill provides structured SQLMap commands, authorization checks, validation steps, and reporting guidance for approved assessments.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Do not auto-install this skill.

The canonical policy requires operator review before any installation action.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "webapp-sqlmap" from https://skillstore.io/skills/agentsecops-webapp-sqlmap.md and its manifest at https://skillstore.io/api/skills/agentsecops-webapp-sqlmap/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/agentsecops-webapp-sqlmap.md Signed manifest GET /api/skills/agentsecops-webapp-sqlmap/manifest Signed lockfile GET /api/skills/agentsecops-webapp-sqlmap/lockfile

Test it

Using "webapp-sqlmap". Review an authorized staging endpoint with one numeric query parameter.

Expected outcome:

Scope confirmed for the named staging host and parameter.
Begin with low-risk detection and a single technique.
Record response differences, request volume, and manual verification results.

Using "webapp-sqlmap". Plan testing for an authenticated JSON API during a maintenance window.

Expected outcome:

Use the supplied request structure and approved authentication header.
Apply the engagement rate limit and stop on instability.
Request confirmation before enumerating database objects or extracting records.

Using "webapp-sqlmap". Turn a confirmed SQL injection result into a report.

Expected outcome:

Summarize the affected endpoint, parameter, technique, and verified impact.
Redact credentials and sampled records from shared evidence.
Recommend parameterized queries, input validation, and least-privilege database access.

Security Audit

Critical

v9 • 7/23/2026 Open versioned report

Most alerts are false positives from Markdown fences, reserved example URLs, educational vulnerable code, and standard output paths. Confirmed issues include a remote script piped to Bash, a third-party action receiving a token, and commands for host file access and OS execution. Semantic review also found web-shell deployment, WAF evasion, and bulk credential extraction guidance that needs stronger controls.

Files scanned

1,994

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (6)

Critical

assets/ci-config-template.yml:240

Pipe to shell pattern

curl -s https://raw.githubusercontent.com/aquasecurity/tfsec/master/scripts/install_linux.sh | bash

The workflow pipes an unauthenticated download directly into Bash without a pinned version or checksum. A compromised source can execute arbitrary code in the CI runner.

Critical

SKILL.md:194

System password file access

sqlmap -u "http://example.com/page?id=1" --file-read="/etc/passwd"

The skill provides a SQLMap command that reads /etc/passwd from the target server. This is direct host file access and can expose system account information.

Critical

SKILL.md:196-209

Remote Host Compromise Workflow

The skill instructs users to deploy shell.php into a web root and obtain operating-system or SQL shells. These actions enable arbitrary remote control.

The commands explicitly use file-write, os-shell, and sql-shell options against a target. The surrounding heading labels them as advanced exploitation.

High

SKILL.md:203

System reconnaissance

sqlmap -u "http://example.com/page?id=1" --os-cmd="whoami"

The documented SQLMap command executes whoami on the target host. Remote operating-system command execution is a high-impact capability even in an authorized testing context.

High

SKILL.md:221-245 SKILL.md:406-417

Defense Evasion and Anonymization Guidance

The skill teaches WAF evasion with tamper scripts, randomized agents, proxies, Tor, and method changes. This can help bypass defensive monitoring.

The sections explicitly say to evade web application firewalls and address WAF blocking. The listed options implement evasion and traffic concealment.

High

SKILL.md:166-184 SKILL.md:307-353

Bulk Credential and Database Extraction

The skill provides commands to dump entire databases, search password columns, extract administrator credentials, and enumerate database passwords and privileges.

The documented commands explicitly request dump-all, password columns, credential extraction, users, passwords, privileges, and all databases.

Capability review items (2)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High

assets/ci-config-template.yml:164

Git platform tokens

GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

The workflow passes GITHUB_TOKEN to gitleaks/gitleaks-action@v2, which is pinned only to a mutable tag. A compromised action could misuse the token despite the workflow's limited permissions.

Low

assets/ci-config-template.yml:240

Hardcoded URL

curl -s https://raw.githubusercontent.com/aquasecurity/tfsec/master/scripts/install_linux.sh | bash

The workflow downloads an installer from a hardcoded remote GitHub URL. This creates a real network and supply-chain dependency.

Risk Factors

⚙️ External commands (50)

🌐 Network access (50)

📁 Filesystem access (4)

assets/ci-config-template.yml:323 assets/ci-config-template.yml:323 SKILL.md:270 SKILL.md:270

🔑 Env variables (23)

⚡ Contains scripts (2)

references/EXAMPLE.md:138 references/EXAMPLE.md:137

Detected Patterns

Pipe to shell patternSystem password file accessSystem reconnaissance

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/agentsecops-webapp-sqlmap/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/agentsecops-webapp-sqlmap/security.svg)](https://skillstore.io/skills/agentsecops-webapp-sqlmap?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/agentsecops-webapp-sqlmap?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/agentsecops-webapp-sqlmap/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/agentsecops-webapp-sqlmap.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

AgentSecOps. (2026). webapp-sqlmap security audit report (audit version 9) [Author version 0.1.0]. Skillstore. https://skillstore.io/skills/agentsecops-webapp-sqlmap/audits/9

BibTeX citation

@techreport{agentsecops-agentsecops-webapp-sqlmap-2026,
  author = {AgentSecOps},
  title = {webapp-sqlmap security audit report (audit version 9)},
  institution = {Skillstore},
  year = {2026},
  number = {9},
  url = {https://skillstore.io/skills/agentsecops-webapp-sqlmap/audits/9},
  note = {Author version 0.1.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "webapp-sqlmap security audit report (audit version 9)"
version: "0.1.0"
type: report
authors:
  - name: "AgentSecOps"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/agentsecops-webapp-sqlmap/audits/9"
identifiers:
  - type: other
    value: "skillstore:agentsecops-webapp-sqlmap:audit:9"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Validate a Staging Endpoint

Create a low-risk detection plan for an approved parameter and record reproducible evidence.

Add Controlled CI Testing

Define scoped SQL injection checks, rate limits, artifacts, and failure criteria for a test environment.

Confirm and Remediate a Finding

Verify a suspected injection flaw, classify impact, and produce defensive remediation guidance.

Try These Prompts

Plan a Basic Parameter Test

Within my written authorization for [target], prepare a minimal SQLMap detection plan for [parameter]. Start with low-risk checks and explain each option.

Test a Saved Request

I have an authorized request file at [path]. Design a staged SQLMap workflow to identify the DBMS and enumerate only [approved objects].

Assess an Authenticated API

Analyze this authorized API request: [request details]. Propose SQLMap options for JSON input, authentication headers, rate limits, and reliable false-positive checks.

Design a Controlled Engagement

For engagement [name], create a controlled SQLMap validation plan for [scope]. Require confirmation before extraction, file access, evasion, or command execution.

Best Practices

Confirm written authorization, target scope, testing window, and data handling rules before any request.
Start with low-risk detection, limit requests, and require approval before extraction or host interaction.
Redact sensitive evidence, preserve an audit log, and verify every automated finding manually.

Avoid

Do not test public, production, or third-party systems without explicit written permission.
Do not begin with bulk dumping, file writes, shell access, WAF evasion, or maximum risk settings.
Do not place real credentials, tokens, personal data, or complete database dumps in prompts or reports.

Frequently Asked Questions

Is written authorization required?

Yes. Use this skill only for systems you own or have explicit written permission to test.

Does this skill install SQLMap?

No. It provides workflows and command guidance. SQLMap and Python must already be available.

Can it test production systems?

Production testing is risky. Use a staging environment unless the approved scope, backups, monitoring, and rollback plan explicitly cover production.

Which request types are supported?

The guidance covers GET, POST, JSON APIs, cookies, headers, authentication, proxies, and saved HTTP request files.

Does it prevent destructive actions?

No. SQLMap options can alter data or remote files. Human review and explicit approval remain necessary.

How should extracted data be handled?

Follow engagement rules, collect the minimum evidence, encrypt storage, restrict access, redact reports, and delete data according to the retention plan.