Skip to content

Bug bounty program

Platform
HackerOne
Bounties
None
Assets in scope
3
Disclosed reports
5
Subdomains
7
Vendor on CyberSIXT
OpenMage (47 CVEs, 0 exploited)

Most upvoted reports5

Most upvoted reports of OpenMage
ReportWeaknessDisclosedBountyVotes
Sharing products with Mail allows phishing attacks due to misconfiguration.Analysed#1083923Input Validation and Logic2021-04-25–38
No error thrown when IDOR attempted while editing addressAnalysed#1085743Misconfiguration and Insecure Design2021-04-26–33
CSRF in changing password after using reset password link#1086752Cross-Site Request Forgery2021-05-27–24
Very long names on demo.openmage.org could redirect victim users to malicious url redirects via email contacts.#1091957Information Disclosure2021-04-29–14
No Limit on Email Subscription#1085079Denial of Service2021-09-04–12

Subdomains7

Subdomains of OpenMage
NameScopeFirst seen
demo-admin.openmage.orgadmin, testNot in the scope2026-11-14
docs.openmage.orgNot in the scope2026-11-14
migrate.openmage.orgNot in the scope2026-11-14
nginxdemo.openmage.orgNot in the scope2026-11-14
nginxdemo-admin.openmage.orgadminNot in the scope2026-11-14

1 names are covered by the program's own scope; 0 were first seen this week. Names come from ProjectDiscovery's public Chaos dataset (passive sources: certificate logs, DNS and other public data), matched to the program by its listing and its own domain scope. A name being in a dataset is not permission to test it: only what the program's own scope says is in scope, and its policy decides. CyberSIXT does not resolve, probe or scan these names. Tags come from the name alone. Source: ProjectDiscovery Chaos. Subdomains on the Atlas, or search the subdomains of every program.

A name in a dataset is not permission to test it: the program's own scope and rules decide. Data as of 2026-11-15.