Bug bounty program
PU
PUBG
Most upvoted reports3
| Report | Weakness | Disclosed | Bounty | Votes |
|---|---|---|---|---|
| Reflected XSS in pubg.comAnalysed#751870 | Cross-site Scripting | 2019-12-09 | – | 102 |
| RXSS to Stored XSS - forums.pubg.com | URL parameterAnalysed#756697 | Cross-site Scripting | 2020-01-02 | – | 100 |
| Reflected XSS in https://lite.pubg.comAnalysed#751284 | Cross-site Scripting | 2019-12-09 | – | 48 |
Subdomains132
| Name | Scope | First seen |
|---|---|---|
| esports-web-cms.pubg.comadmin | In scope | 2026-11-14 |
| global-esports-cms.pubg.comadmin | In scope | 2026-11-14 |
| administrator.support.pubg.comadmin | In scope | 2026-11-14 |
132 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.