performing-exploit-verification

Verifies suspected vulnerabilities with reproducible exploit proof before reporting findings.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill performing-exploit-verification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performing-exploit-verification
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/penetration-testing/performing-exploit-verification
Command: npx skills add https://github.com/xalgord/xalgorix --skill performing-exploit-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated scanners and initial exploit attempts often produce ambiguous or false-positive results, leading to unreliable vulnerability reports. This Skill enforces a systematic verify-before-report methodology so every finding is backed by concrete, reproducible proof.

Core Features & Use Cases

  • Category-Based Verification: Classifies findings into five categories (data extraction, reflected content, behavioral, access control, code execution) and applies the matching proof standard for each.
  • Per-Vulnerability Playbooks: Provides step-by-step confirmation procedures for SQL injection, XSS, SSRF, IDOR, and RCE using curl, sqlmap, Burp Suite, and out-of-band callbacks.
  • False Positive Elimination: Enforces baseline-exploit-control comparisons, proportional timing checks, two-session IDOR testing, and encoding-vs-reflection analysis before any finding is reported.
  • Use Case: After nuclei flags a possible time-based SQL injection, use this Skill to run SLEEP(0)/SLEEP(3)/SLEEP(7) proportional timing tests, confirm with sqlmap data extraction, and document a structured verification record.

Quick Start

Verify whether the suspected SQL injection at the target's id parameter is real by running baseline, exploit, and control requests and documenting the proof.

Frequently Asked Questions about performing-exploit-verification

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

FAQPage Schema
How do I verify a SQL injection vulnerability manually?

Verify SQL injection by comparing a baseline request against a quote-injected request, then confirming with time-based payloads like SLEEP(5) versus a SLEEP(0) control. For definitive proof, use sqlmap to extract database names, which constitutes data-extraction-level evidence.

How to confirm time-based blind SQL injection is not network jitter?

Confirm blind SQL injection with proportional timing tests: run SLEEP(0), SLEEP(3), and SLEEP(7) and check that response delays scale with the sleep value. Repeat the test two to three times and compare against a baseline to rule out network variance.

What tools are needed for exploit verification in penetration testing?

The methodology uses curl for HTTP-level verification, sqlmap for SQL injection confirmation, Burp Suite for request replay, Python 3 for custom scripts, and an out-of-band callback service such as Burp Collaborator or webhook.site for SSRF and blind RCE confirmation.

Why is reflected input in a page not always XSS?

Reflected input is not XSS when the framework HTML-encodes the payload, such as returning &lt;script&gt; instead of raw <script>. Confirm the payload appears unencoded in an executable context, and for DOM XSS verify actual execution in a browser.

How do I test for IDOR without false positives?

Test IDOR with two authenticated sessions: have User A request User B's resource using A's token. Accessing your own object with a changed ID or testing unauthenticated does not prove IDOR; only cross-user data exposure confirms it.

When should a scanner finding be treated as a false positive?

Treat a scanner finding as a false positive when manual replay shows a WAF blocking the payload, the response difference comes from dynamic content like timestamps, or the exploit cannot be reproduced three times with a diverging control test.