Skip to content

weakness in SQL Injection

SQL Injection

3 disclosed reports · $7,500 paid · 3 valid

Every dot is a report; the named ones are the most upvoted. Bright dots were paid a bounty; faint ones HackerOne no longer shows to the public. 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
3
valid
3
paid a bounty
1
no longer public
1

Every one of the 3 is a mark on the map. Named now: 1 to 3, most upvoted first.

  1. Blind SQLi leading to RCE, from Unauthenticated access to a test API Webservice#592400Starbucks · 236 votesValid
  2. SQL Injection [unauthenticated] with direct output at https://news.mail.ru/#818972Mail.ru · $7,500 · 156 votesno longer publicHackerOne no longer shows this report to the public (checked 2026-11-14). Its title and metadata are kept here.
  3. Unauthenticated SQL Injection at █████████ [HtUS]#1626226U.S. Dept Of Defense · 61 votesValid

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.