Skip to content

Bug bounty reports15,219

Publicly disclosed HackerOne reports, with the platform's own outcome and severity.

Program:Stellar.org
Status
Severity
Weakness
Year
Bounty paid0
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
  • No account0
  • A user account0
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Clear filters10 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Admin panel of https://www.stellar.org/wp-admin/#376563N/AMisconfiguration and Insecure Design–2020-02-23–3
Session Cookie without HttpOnly and secure flag set#239380InformativeMisconfiguration and Insecure Design–2017-06-14–4
xss#281387InformativeNo weakness recorded–2020-02-23–6
HTTP - Basic Authentication on https://www.stellar.org/wp-login.php#239479N/AMisconfiguration and Insecure Design–2017-06-13–7
heap-buffer-overflow (READ of size 1) in cpptoml::parser::consume_whitespace()#240659ValidMemory Corruption–2017-06-30–8
Bypassing Verify Humans Page#242874InformativeAuthentication–2020-02-23–8
Direct URL access to PDF files#263780InformativeAccess Control–2020-02-23–10
It's possible to put SDX orderbook into invalid state and execute trades at arbitrary price#321511ValidInput Validation and Logic–2018-10-14–12
brute force attack allowed on admin page https://www.stellar.org/wp-admin/#342977InformativeAuthentication–2020-02-23–16
Exploitable vulnerability in SDEX#330105ValidInput Validation and Logic–2018-10-14–29

Status and severity are HackerOne's. “Access stated” is what the title says; “Access needed” and techniques come from CyberSIXT's analysis of the public report (227 analysed so far), which can be wrong. Data as of 2026-11-14.

Updated AboutDevelopersSign in