security-audit
在IBL5 PHP代码中检测和修复XSS和SQL注入安全漏洞。适用于安全审计、修复漏洞或审查代码中的安全问题。
📖 中文导读:在IBL5 PHP代码中检测和修复XSS和SQL注入安全漏洞。适用于安全审计、修复漏洞或审查代码中的安全问题。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
name: security-audit description: Security vulnerability detection and remediation for XSS and SQL injection in IBL5 PHP code. Use when auditing security, fixing vulnerabilities, or reviewing code for security issues.
IBL5 Security Audit
Identify and fix SQL injection, XSS, and input validation vulnerabilities.
Primary Vulnerability Checks
1. SQL Injection
Vulnerable patterns:
// ❌ VULNERABLE - String interpolation
$query = "SELECT * FROM table WHERE id = $id";
$query = "SELECT * FROM table WHERE name = '$name'";
Secure patterns:
// ✅ SECURE - Prepared statements (modern mysqli)
$stmt = $db->prepare("SELECT * FROM table WHERE id = ?");
$stmt->bind_param('i', $id);
// ✅ SECURE - Escaped strings (legacy sql_* methods)
$escaped = \Services\DatabaseService::escapeString($db, $input);
2. XSS (Cross-Site Scripting)
Vulnerable patterns:
// ❌ VULNERABLE - Direct output
echo $username;
<?= $row['name'] ?>
Secure patterns:
// ✅ SECURE - Use HtmlSanitizer
echo \Utilities\HtmlSanitizer::safeHtmlOutput($username);
<?= \Utilities\HtmlSanitizer::safeHtmlOutput($row['name']) ?>
3. Input Validation
Vulnerable patterns:
// ❌ VULNERABLE - No validation
$playerId = $_GET['pid'];
$sortColumn = $_GET['sort'];
$query = "ORDER BY $sortColumn";
Secure patterns:
// ✅ SECURE - Type casting and whitelist
$playerId = filter_input(INPUT_GET, 'pid', FILTER_VALIDATE_INT);
$allowedColumns = ['name', 'age', 'position'];
$sortColumn = in_array($_GET['sort'], $allowedColumns, true)
? $_GET['sort'] : 'name';
Audit Checklist
Database Operations
- All queries use prepared statements OR properly escaped values
- No string interpolation with user input in SQL
- Dynamic table/column names validated against whitelist
- LIMIT/OFFSET values are integers
Output Encoding
- All user-controlled output uses
HtmlSanitizer::safeHtmlOutput() - HTML attributes properly escaped
- JavaScript contexts use
json_encode()for data
Input Validation
- Integer inputs validated with
filter_var()or type casting - Enumerated values checked against whitelist
- String inputs have maximum length limits
Report Format
## [SEVERITY] Vulnerability Type - filename.php:line
**Location:** `ClassName::methodName()`
**Vulnerable Code:**
// Show the problematic code
**Risk:** What an attacker could do
**Recommended Fix:**
// Show the secure version
Severity: CRITICAL (SQL injection) | HIGH (XSS) | MEDIUM (validation) | LOW (best practice)
Examples
See examples/ for before/after patterns:
Secured Reference Modules
ibl5/classes/PlayerSearch/- 15+ injection points fixedibl5/classes/DepthChart/SECURITY.md- Security patterns documented