explaingit

fuzzdb-project/fuzzdb

8,902PHPAudience · ops devopsComplexity · 2/5LicenseSetup · easy

TLDR

A large library of text-based attack patterns, directory discovery wordlists, and response-matching rules that security testers feed into tools like Burp Suite and OWASP ZAP to find vulnerabilities in web applications.

Mindmap

mindmap
  root((FuzzDB))
    Attack patterns
      SQL injection
      XSS payloads
      Auth bypass
    Discovery
      File names
      Admin panels
      Config files
    Response analysis
      Error patterns
      Regex matchers
    Used with
      Burp Suite
      OWASP ZAP
      Metasploit
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Load SQL injection and XSS payload lists into Burp Suite or OWASP ZAP to test a web application for input vulnerabilities.

USE CASE 2

Use directory discovery wordlists to find hidden admin panels, log files, and config files left on a server.

USE CASE 3

Apply response analysis regex patterns to scan server responses for leaked credentials or sensitive data.

Tech stack

PHP

Getting it running

Difficulty · easy Time to first run · 5min

Antivirus software will flag the files, this is expected given the content, do not store on a production server.

Free to use and redistribute under the New BSD License and Creative Commons Attribution, credit the project when using it in your work or products.

In plain English

FuzzDB is a large collection of text files used by security testers to find weaknesses in web applications and other software. It is not a program you run on its own. Instead, it is a library of test inputs, patterns, and lists that you feed into security testing tools to see how a target application responds to unusual or malicious input. The collection is organized into three main categories. Attack patterns are lists of strings that have historically caused applications to misbehave: things like SQL injection payloads, scripts that could trigger cross-site scripting (XSS) vulnerabilities, inputs that expose files on a server, authentication bypass tricks, and many others. Discovery lists contain common file and directory names that administrators often leave in predictable locations, such as log files, admin panels, and configuration files, sorted by platform and application type. Response analysis contains regular expressions you can use to search server responses for signs of success, such as error messages, credit card numbers, or social security number patterns. The repository also includes webshells (scripts attackers sometimes upload to gain control of a server), common username and password lists, and other wordlists useful during penetration testing. Many directories contain their own notes explaining how to use the contents. Security testers use FuzzDB alongside tools like Burp Suite, OWASP ZAP, and Metasploit. It is already bundled into several well-known security tools and Linux distributions aimed at security professionals. The README warns that antivirus software may flag the files, which is expected given the content, and advises against storing the repository on a production server. The project was created in 2010 and is licensed under a combination of the New BSD License and Creative Commons Attribution. Anyone using FuzzDB in their work or products is asked to credit the project.

Copy-paste prompts

Prompt 1
I'm running a Burp Suite scan on my own web app, which FuzzDB attack lists should I use to test for SQL injection and XSS vulnerabilities?
Prompt 2
Help me write a Python script that reads a FuzzDB password wordlist and tests login credentials against an endpoint I own and am authorized to test.
Prompt 3
Using FuzzDB's directory discovery lists with OWASP ZAP, how do I find hidden admin pages on my own site?
Open on GitHub → Explain another repo

← fuzzdb-project on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.