weakness in SQL Injection
SQL Injection
8 disclosed reports · $0 paid · 8 valid
Every dot is a report; the named ones are the most upvoted. Bright dots were paid a bounty. A report opens its page here: our analysis where there is one, and the link to HackerOne. The status is HackerOne's own outcome; "access needed" is only what a title states.
- reports
- 8
- valid
- 8
- paid a bounty
- 0
Every one of the 8 is a mark on the map. Named now: 1 to 8, most upvoted first.
- [intensedebate.com] SQL Injection Time Based On /js/commentAction/
- SQL injection in URL path leads to Database Access
- SQL Injection when using FilteredRelation
- Woocommerce SQL Injection in WC_Report_Coupon_Usage
- Error-Based & Time-Based SQL Injection in 'keyword' Parameter of admin-search.php Allowing Full Database Access in Revive Adserver v6.0.0
- SQL Injection in CVE Discovery Search
- SQL Injection in Django ORM via Unvalidated `_connector` in Q Objects
- SQL injection in JSONField KeyTransform
paid a bounty
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-14 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.