payloadsallthethings
4.2 open-sourceThe section your link pointed to isn't on payloadsallthethings's page any more, so we've brought you to the top.
Collection of web application security payloads and bypasses covering common vulnerabilities for use in penetration testing.
Summary
payloadsallthethings is an open-source reference of payloads, bypasses, and exploitation techniques for web application security, maintained as a collection of markdown cheatsheets you browse on GitHub or its companion documentation site rather than a tool you install or run. Each vulnerability class gets its own folder with a README explaining the technique, ready-made payloads, and files formatted for direct use in Burp Intruder, which makes it most useful to penetration testers and red teamers during hands-on engagements rather than to teams building automated scanning pipelines. It sits in the same family as the author's InternalAllTheThings and HardwareAllTheThings wikis, covering the web-exploitation side of that set: injection, deserializationdeserializationTurning stored or transmitted data back into objects a program can use. Unsafe handling of untrusted data can allow unexpected behavior or code execution., file inclusion, and similar bypass classes. With 342 contributors, 61 commits in the past year, and a last release 391 days ago, it remains actively maintained community reference material rather than an abandoned wiki.
Collection of web application security payloads and bypasses covering common vulnerabilities for use in penetration testing.
How payloadsallthethings helps
How do I turn a confirmed injection point into a working proof of concept during an engagement?
the matching folder pairs an explanation of the technique with ready-made payload lists formatted for direct use in Burp Intruder, so the payload set can be dropped straight into a fuzzing run
Are there known bypasses for a specific web server or language-level filter I'm up against?
topic pages such as reverse proxy misconfiguration or command injection filter evasion document the specific bypass patterns and character tricks that defeat common filtering setups
How do I exfiltrate data through a channel that only accepts spreadsheet formulas or similar constrained input?
the CSV injection material covers formula-based techniques like IMPORTXML and IMPORTRANGE for pulling data out through that specific vector
What is the state of the art for reading files blindly through a file inclusion bug?
the file inclusion section documents blind file read primitives and points to tooling built for that exact scenario, saving the work of rediscovering the technique mid-engagement
Languages
Command line
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for payloadsallthethings, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail payloadsallthethings puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
2 entries
No entries match these filters.
- July 20251
- April 20241
Project health
Issue, contributor and maintainer activity in swisskyrepo/PayloadsAllTheThings, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 18 −4 vs prior 12 months
- Maintainers 2 +1 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed not measured of issues opened, last 12 months
- Median time to close not measured issues closed, last 12 months
- Open backlog not measured open issues today
- Issues opened / month not measured
- Open backlog not measured
- Contributors / month 0
- Commits / month 0
- Stars 80,987
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →