tools

Overview

Burp Repeater manually replays any captured HTTP request, allowing rapid parameter changes and repeated submission without re-navigating the application. The primary tool for manual payload testing, endpoint exploration, and confirming vulnerabilities before escalating to automated scanning.

Target / Context

Individual HTTP requests captured by Burp Proxy. Used throughout web application testing whenever a specific request needs repeated testing with varied inputs.


Installation

ℹ︎Installation Commands:

Part of Burp Suite — see Burp Suite for installation.


Basic Usage

ℹ︎Basic Usage:
  1. In the Proxy Intercept pane or HTTP History, right-click a request → Send to Repeater (CTRL+R)
  2. Navigate to Repeater tab (CTRL+SHIFT+R)
  3. Modify the request — edit parameters, headers, body, or method
  4. Click Send — the response appears in the right pane

Flags & Options

ℹ︎Repeater Controls:
ActionShortcut / Location
Send to RepeaterCTRL+R from anywhere in Burp
Navigate to Repeater tabCTRL+SHIFT+R
Change HTTP methodMethod dropdown in request pane — toggles GET/POST without rewriting the request
URL-encode selected textSelect text → CTRL+U (or right-click → Convert Selection → URL → URL-encode key characters)
Encode while typingRight-click → enable “URL-encode as you type”

Common Use Cases

Manual Payload Testing

ℹ︎Example — SQL Injection:
  1. Capture a login POST request in Proxy
  2. CTRL+R to send to Repeater
  3. Replace the password value with ’ OR 1=1— -
  4. Click Send — inspect the response for authentication bypass indicators (redirect, welcome message, changed body length)

Bypass Client-Side Input Filters

ℹ︎Example — XSS via Numeric Field:
  1. Submit valid data through a number-only form field to capture the request in Proxy
  2. CTRL+R to send to Repeater
  3. Replace the numeric parameter value with <script>alert(“XSS”)</script>
  4. URL-encode the payload: CTRL+U
  5. Send — if the server doesn’t validate input type server-side, the payload executes

Encoding and Decoding

Burp Inspector (accessible within Repeater) handles inline encoding/decoding as you edit. For bulk or multi-step encoding operations, use the standalone Decoder tab.

ℹ︎Supported Encoding Schemes:
SchemeCommon Use
URL encodingRequired for special characters in query strings and form data
Full URL encodingEncodes every character, not just key characters
Unicode URL encodingUsed for WAF bypass (%u0027 for single quote)
HTML encodingFor XSS payload preparation or testing HTML injection
Base64Cookie, token, and binary data manipulation
ASCII HexFor binary and raw byte data representation
ℹ︎Decoder Tab:

Paste input → select encoding/decoding scheme → output is immediately shown Chain multiple transforms by copying output and pasting into a new input field Useful for multi-layered encoding like Base64-encoded JSON containing URL-encoded values



References / Images