Skip to content
Documentation
Skill

/burp-suite-testing

This skill should be used when the user asks to "intercept HTTP traffic", "modify web requests", "use Burp Suite for testing", "perform web vulnerability scanning", "test with Burp Repeater", "analyze HTTP history", or "configure proxy for web testing". It provides comprehensive

From plugin
claude-code-guide
4.7k78 skills

Claude Code

$ npx -y skills add zebbern/claude-code-guide --skill burp-suite-testing --agent claude-code

SKILL.md

burp-suite-testing.SKILL.md
name: burp-suite-testing
description: This skill should be used when the user asks to "intercept HTTP traffic", "modify web requests", "use Burp Suite for testing", "perform web vulnerability scanning", "test with Burp Repeater", "analyze HTTP history", or "configure proxy for web testing". It provides comprehensive guidance for using Burp Suite's core features for web application security testing.
metadata:
  author: zebbern
  version: "1.1"

Burp Suite Web Application Testing

Purpose

Execute comprehensive web application security testing using Burp Suite's integrated toolset, including HTTP traffic interception and modification, request analysis and replay, automated vulnerability scanning, and manual testing workflows. This skill enables systematic discovery and exploitation of web application vulnerabilities through proxy-based testing methodology.

Inputs / Prerequisites

Required Tools

  • Burp Suite Community or Professional Edition installed
  • Burp's embedded browser or configured external browser
  • Target web application URL
  • Valid credentials for authenticated testing (if applicable)

Environment Setup

  • Burp Suite launched with temporary or named project
  • Proxy listener active on 127.0.0.1:8080 (default)
  • Browser configured to use Burp proxy (or use Burp's browser)
  • CA certificate installed for HTTPS interception

Editions Comparison

| Feature | Community | Professional | |---------|-----------|--------------| | Proxy | ✓ | ✓ | | Repeater | ✓ | ✓ | | Intruder | Limited | Full | | Scanner | ✗ | ✓ | | Extensions | ✓ | ✓ |

Outputs / Deliverables

Primary Outputs

  • Intercepted and modified HTTP requests/responses
  • Vulnerability scan reports with remediation advice
  • HTTP history and site map documentation
  • Proof-of-concept exploits for identified vulnerabilities

Core Workflow

Phase 1: Intercepting HTTP Traffic

Launch Burp's Browser

Navigate to integrated browser for seamless proxy integration:

1. Open Burp Suite and create/open project 2. Go to **Proxy > Intercept** tab 3. Click **Open Browser** to launch preconfigured browser 4. Position windows to view both Burp and browser simultaneously

Configure Interception

Control which requests are captured:

Proxy > Intercept > Intercept is on/off toggle

When ON: Requests pause for review/modification
When OFF: Requests pass through, logged to history

Intercept and Forward Requests

Process intercepted traffic:

1. Set intercept toggle to **Intercept on** 2. Navigate to target URL in browser 3. Observe request held in Proxy > Intercept tab 4. Review request contents (headers, parameters, body) 5. Click **Forward** to send request to server 6. Continue forwarding subsequent requests until page loads

View HTTP History

Access complete traffic log:

1. Go to **Proxy > HTTP history** tab 2. Click any entry to view full request/response 3. Sort by clicking column headers (# for chronological order) 4. Use filters to focus on relevant traffic

Phase 2: Modifying Requests

Intercept and Modify

Change request parameters before forwarding:

1. Enable interception: **Intercept on** 2. Trigger target request in browser 3. Locate parameter to modify in intercepted request 4. Edit value directly in request editor 5. Click **Forward** to send modified request

Common Modification Targets

| Target | Example | Purpose | |--------|---------|---------| | Price parameters | `price=1` | Test business logic | | User IDs | `userId=admin` | Test access control | | Quantity values | `qty=-1` | Test input validation | | Hidden fields | `isAdmin=true` | Test privilege escalation |

Example: Price Manipulation

POST /cart HTTP/1.1
Host: target.com
Content-Type: application/x-www-form-urlencoded

productId=1&quantity=1&price=100

# Modify to:
productId=1&quantity=1&price=1

Result: Item added to cart at modified price.

Phase 3: Setting Target Scope

Define Scope

Focus testing on specific target:

1. Go to **Target > Site map** 2. Right-click target host in left panel 3. Select **Add to scope** 4. When prompted, click **Yes** to exclude out-of-scope traffic

Filter by Scope

Remove noise from HTTP history:

1. Click display filter above HTTP history 2. Select **Show only in-scope items** 3. History now shows only target site traffic

Scope Benefits

  • Reduces clutter from third-party requests
  • Prevents accidental testing of out-of-scope sites
  • Improves scanning efficiency
  • Creates cleaner reports

Phase 4: Using Burp Repeater

Send Request to Repeater

Prepare request for manual testing:

1. Identify interesting request in HTTP history 2. Right-click request and select **Send to Repeater** 3. Go to **Repeater** tab to access request

Modify and Resend

Test different inputs efficiently:

1. View request in Repeater tab
2. Modify parameter values
3. Click Send to submit request
4. Review response in right panel
5. Use navigation arrows to review request history

Repeater Testing Workflow

Original Request:
GET /product?productId=1 HTTP/1.1

Test 1: productId=2    → Valid product response
Test 2: productId=999  → Not Found response  
Test 3: productId='    → Error/exception response
Test 4: productId=1 OR 1=1 → SQL injection test

Analyze Responses

Look for indicators of vulnerabilities:

  • Error messages revealing stack traces
  • Framework/version information disclosure
  • Different response lengths indicating logic flaws
  • Timing differences suggesting blind injection
  • Unexpected data in responses

Phase 5: Running Automated Scans

Launch New Scan

Initiate vulnerability scanning (Professional only):

1. Go to **Dashboard** tab 2. Click **New scan** 3. Enter target URL in **URLs to scan** field 4. Configure scan settings

Scan Configuration Options

| Mode | Description | Duration | |------|-------------|----------| | Lightweight | High-level overview | ~15 minutes | | Fast | Quick vul

Read more
@zebbern
Ships withclaude-code-guide

Claude Code Guide - Setup, Commands, workflows, agents, skills & tips-n-tricks from beginner to power user!

Stars on GitHub

Momentum

stars in total
4.7k
Star history of zebbern/claude-code-guide on GitHub, a chart by star-history.com

Other skills on claude-code-guide.

audit-flow

audit-flow

Interactive system flow tracing across CODE, API, AUTH, DATA, NETWORK layers with SQLite persistence and Mermaid export. Use for…

More skills from other plugins.

context7-cli

context7-cli

Use the ctx7 CLI to fetch library documentation and configure Context7 MCP. Activate when the user mentions "ctx7" or "context7",…

context711d64k
@upstash@upstashInstall Skill
docs-components

docs-components

Comprehensive MDX component patterns (Note, Pitfall, DeepDive, Recipes, etc.) for all documentation types. Authoritative source…

@reactjs@reactjsInstall Skill
codebase-wiki

codebase-wiki

How to work in a Codebase Wiki project (the `codebase-wiki` starter pack): an agent-authored, source-grounded wiki of the…

@inkeep@inkeepInstall Skill
omm-push

omm-push

Push architecture docs to oh-my-mermaid cloud. Handles login, link, and push workflow with error guidance. Use when the user says…

@oh-my-mermaid@oh-my-mermaidInstall Skill

Questions about burp-suite-testing.

Which coding agents can use burp-suite-testing?
burp-suite-testing installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.