exploiting-with-burp

Validates access control, session, SSRF, and path traversal flaws via Burp Suite MCP.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/bs-koo/gx-security --skill exploiting-with-burp-bs-koo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: exploiting-with-burp
Source: https://github.com/bs-koo/gx-security/tree/main/skills/exploiting-with-burp
Command: npx skills add https://github.com/bs-koo/gx-security --skill exploiting-with-burp-bs-koo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Authorized penetration testers need to dynamically confirm whether access control (IDOR/BFLA), authentication/session, SSRF, and path traversal vulnerabilities found in source code are actually exploitable, while keeping all traffic auditable and scope-enforced. This Skill routes existing deterministic attack scripts through the Burp Suite proxy and adds Burp MCP tools for deeper interactive verification. ## Core Features & Use Cases - Hybrid proxy-routed exploitation: Runs existing attack_*.py scripts through the Burp proxy (127.0.0.1:8080) so scope_guard enforcement, deterministic verdicts, and reporting stay intact while traffic accumulates in Burp history. - MCP-assisted deep dives: Uses Burp MCP tools such as send_http1_request, proxy history queries, url_encode, and Collaborator payloads to deepen confirmed findings, with mandatory scope_guard pre-validation of target hosts. - Use Case: After a static scan flags a potential IDOR on a staging server, run the audit script with --burp-proxy, capture user A's session request from Burp history, swap in user B's token, and confirm whether a 200 response with another user's data proves the vulnerability. ## Quick Start Ask the AI to verify access control and session vulnerabilities on http://localhost:8080 through the Burp proxy after running the burp_preflight check.

Frequently Asked Questions about exploiting-with-burp

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

FAQPage Schema
How do I route penetration test scripts through Burp Suite proxy?▼

Set the SECURITY_PLUGIN_BURP_PROXY environment variable to http://127.0.0.1:8080, or pass --burp-proxy to the audit script. All attack_*.py scripts inherit the proxy setting, and scope_guard enforcement plus verdict logic remain unchanged.

How do I test IDOR vulnerabilities with Burp MCP tools?▼

Capture user A's session request from Burp proxy history, replace the cookie or token with user B's, then fire it with send_http1_request. A 403 response confirms a false positive; only a 200 returning another user's data confirms the vulnerability.

Does Burp MCP support JWT token manipulation?▼

No, Burp's base64 tools only handle standard base64 and reject the URL-safe characters used in JWTs. Run attack_auth.py through the Burp proxy instead, which handles base64url correctly while still recording traffic in Burp history.

Can I use Burp Suite Community edition for this workflow?▼

Yes, the proxy-routed deterministic path and most MCP tools work with Community edition. Collaborator-based blind SSRF detection is Pro-only, so Community users fall back to the existing oob_canary.py script.

Why do proxied requests hang when using Burp Suite?▼

Burp Proxy Intercept being enabled blocks all proxied traffic. Turn Intercept off manually or call set_proxy_intercept_state(false) via MCP before launching any requests.

When should I not use Burp MCP for exploitation?▼

Avoid it for SQL injection and XSS, which have dedicated skills using sqlmap and Playwright respectively. Also skip it when Burp is not installed, since the standard attack scripts run directly without a proxy.