sql-injection-error

Extract database schemas and sensitive data via error-based SQL injection payloads.

253|37|Updated Feb 22, 2026

Search Tags:#sql injection #penetration testing #web security #data exfiltration #sqlmap #error-based

Ready to run

npx skills add https://github.com/blacklanternsecurity/red-run --skill sql-injection-error

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sql-injection-error
Source: https://github.com/blacklanternsecurity/red-run/tree/main/skills/web/sql-injection-error
Command: npx skills add https://github.com/blacklanternsecurity/red-run --skill sql-injection-error

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps penetration testers leverage verbose database error messages to extract sensitive data from web applications vulnerable to error-based SQL injection.

Core Features & Use Cases

DBMS Fingerprinting: Identifies the database management system (MySQL, MSSQL, PostgreSQL, Oracle) based on error signatures.
Data Extraction: Guides the extraction of users, databases, tables, columns, and sensitive data through specific SQL payloads.
Use Case: When an application reveals detailed SQL errors, use this Skill to systematically query and retrieve user credentials or configuration secrets from the database.

Quick Start

Use the sql-injection-error skill to extract the current user from the identified SQL injection point.

Frequently Asked Questions about sql-injection-error

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I extract database schemas using error-based SQL injection?▼

Error-based SQL injection extracts database schemas by injecting specific payloads into vulnerable inputs, forcing the database to return verbose error messages containing table and column names for data exfiltration.

What is the difference between error-based and blind SQL injection?▼

Error-based SQL injection relies on verbose database error messages to directly exfiltrate data, whereas blind SQL injection requires inferential techniques like time delays or boolean responses when the application suppresses error output.

Can I use error-based SQL injection payloads for MySQL, MSSQL, PostgreSQL, and Oracle?▼

Yes, error-based SQL injection techniques support MySQL, MSSQL, PostgreSQL, and Oracle by leveraging DBMS-specific error signatures and technique-specific payloads to fingerprint the database and extract sensitive data.

How do I fingerprint a DBMS from verbose SQL errors?▼

DBMS fingerprinting from verbose SQL errors involves analyzing unique error signatures returned by the application to identify whether the backend database is MySQL, MSSQL, PostgreSQL, or Oracle.

Do I need a confirmed SQL injection point to extract data using verbose errors?▼

Yes, extracting data using verbose errors requires a confirmed SQL injection point with verbose error output to successfully execute technique-specific payloads and retrieve database schemas, tables, and columns.

When should I not use error-based SQL injection for data exfiltration?▼

You should not use error-based SQL injection when the application suppresses verbose database error messages, as this technique relies entirely on the application returning detailed error output to extract sensitive data.