head to head · open source
PayloadsAllTheThings vs cve
PayloadsAllTheThings has 82,474 GitHub stars, 17,566 forks, 36 open issues and last shipped 10 days ago. cve has 8,192 stars, 982 forks, 21 open issues and last shipped 24 days ago. PayloadsAllTheThings leads on adoption by 907% (82,474 vs 8,192 stars). PayloadsAllTheThings is written in Python under MIT; cve is written in HTML under MIT. PayloadsAllTheThings has attracted 21% as many forks as stars, cve 12%. PayloadsAllTheThings was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (hacking, penetration-testing), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| PayloadsAllTheThings | cve | |
|---|---|---|
| GitHub stars | ★ 82K | ★ 8.2K |
| License | MIT | MIT |
| Written in | Python | HTML |
| Last push | 2026-10-30 | 2026-10-16 |
| Forks | ⑂ 18K | ⑂ 982 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick PayloadsAllTheThings if
- You weight community size — 82K stars and counting
- You want the MIT license terms
- Your stack matches Python
- You value the larger contributor base for long-term maintenance
pick cve if
- You want the cve feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches HTML
- You evaluated both and cve fits your workflow better
About PayloadsAllTheThings
Payloads All The Things A list of useful payloads and bypasses for Web Application Security. Feel free to improve with your payloads and techniques! You can also contribute with a :beers: IRL, or using the sponsor button. An alternative display version is available at PayloadsAllTheThingsWeb. :book: Documentation Every section contains the following files, you can use the template vuln folder to create a new chapter: README.md vulnerability description and how to exploit it, including several payloads Intruder a set of files to give to Burp Intruder Images pictures for the README.md Files some files referenced…
read the full PayloadsAllTheThings overview →
About cve
CVE PoC Almost every publicly available CVE PoC. Current hottest CVEs To see the complete history go here How it works Trickest Workflow Architecture TB; DZ (Too big; didn't zoom): Collect CVE details from cvelist (Shout out to CVE Project!) Split CVEs up by year. Find PoCs for each CVE using 2 techniques: 1. References Gather each CVE's References . Check if any of them points to a PoC using ffuf and a list of keywords Regex: (Thanks @joohoi!) Note : ffuf is awesome for more purposes than just content discovery. Get CVE referenced in HackerOne Reports AllVideoPocsFromHackerOne (Thanks @zeroc00I!) 2. Github…
More in Security & Privacy
Related comparisons
More Threat Detection & Response projects
Compare either of these against the rest of the Threat Detection & Response field.
Frequently asked questions
Is PayloadsAllTheThings or cve more popular?
PayloadsAllTheThings has 82,474 GitHub stars and cve has 8,192. PayloadsAllTheThings has the larger community by that measure.
Are PayloadsAllTheThings and cve free?
Both are open source. PayloadsAllTheThings is licensed under MIT and cve under MIT. Neither carries a licence fee.
What is the difference between PayloadsAllTheThings and cve?
PayloadsAllTheThings is written in Python and cve in HTML. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, PayloadsAllTheThings or cve?
Choose PayloadsAllTheThings if you want the larger community (82,474 stars) or its MIT licence terms. Choose cve if its feature set, stack or MIT licence fits better. Both are self-hostable.