A community collection of application-security test inputs, wordlists, reference examples, and supporting tools for penetration testers and bug bounty researchers.
Start with the category directory that matches your assessment, or browse the complete file catalogue. Existing category names and file paths are retained so bookmarks and tooling remain usable.
For practical file selection and formats, read the input guide. The upstream review compares six established community projects, explains the latest focused additions, and records remaining coverage gaps.
The complete file review records a status for every existing category file, including exact upstream matches, refreshed lists, preserved fixtures, and files whose origin still needs investigation. It distinguishes verified updates from unresolved provenance rather than assuming every file needs new content.
The latest content update details 12,753 sourced additions across 39 existing lists, the forensics-helper fixes, and explicit reasons for preserving other files.
| Area | Categories |
|---|---|
| Application inputs | Command injection, SQL injection, NoSQL injection, LDAP injection, GraphQL injection, Template injection, HTML injection, Insecure deserialization, Remote code execution |
| Browser security | Cross-site scripting, CSRF, CORS, Clickjacking, Content sniffing, Open redirects |
| APIs and application workflows | API security, JWT, OAuth and SSO, WebSockets, Business logic, Race conditions, Prototype pollution |
| HTTP and infrastructure | CRLF, Host headers, Request smuggling, Web caching, Path normalization, SSRF, Subdomain takeover, Management interfaces |
| Files and parsers | File inclusion, File upload, XML external entities, EXIF metadata |
| Discovery and test data | Discovery, Fuzzing, Default and common credentials, Usernames, User agents, Auxiliary data and tools |
| Reference collections | Source-code analysis, Forensics, Shellcode, Web shells |
- Flat wordlists contain independent entries. Preserve their case, whitespace, encoding, and first-occurrence order.
- Examples and request fixtures can span multiple lines. Repeated headers, markup, or delimiters may be required parts of an example.
- Paired and counted datasets can rely on row alignment or occurrence counts. Do not independently sort or deduplicate their columns.
- Imported collections and archives retain their original paths and notices. Identical bytes do not necessarily mean interchangeable filenames or packages.
Review a file before using it, and use these materials only in systems and assessments you are authorised to test. Nothing in this repository needs to be executed to browse or maintain the collection.
The maintenance commands require Python 3.9 or newer and only its standard library. Run them from the repository root:
python3 tools/maintain.py check
python3 tools/review_inventory.py --check
python3 tools/maintain.py audit
python3 -m unittest discover -s tests -vcheck validates reviewed wordlists, catalogue freshness, documented identical-file groups, imported-data and licence hashes, and local file links in maintained documentation. audit reports byte-identical files without deleting them. To clean the explicitly reviewed lists and regenerate navigation:
python3 tools/maintain.py fix
python3 tools/maintain.py catalogSee maintenance policy, the deduplication record, and contribution guidelines. No maintenance command executes payloads, imports archived tools, or sends network requests.
The test suite checks maintenance logic and the forensics helper using synthetic input and stub commands; the helper tests require Bash. The included GitHub Actions workflow runs the same checks and synthetic tests on pull requests and pushes after it is committed. Newly imported datasets have immutable source revisions and retained licence notices in the source registry.
Contributions are welcome. Reuse the closest existing category, explain the purpose of an addition, and include its upstream source and licence when known. Do not submit live credentials or personal data.
Thank you to the open-source projects and community members whose work forms this collection. The root MIT licence and any notices or licences shipped with imported material must be retained; this cleanup does not change upstream licensing.