- Top reward
- $20,000
- Top severity paid
- Critical
- Assets in scope
- 5
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $20,000
- for critical bugs.
- Report on HackerOne
- Submit through the program page.
- Replies within 5 days
- As the policy promises.
- No public write-ups
- Keep findings private.
Rewards
What HackerOne lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$20,000 from $4,000 |
| High |
|
$3,000 from $1,000 |
| Medium |
|
$600 from $200 |
| Low |
|
$200 from $50 |
- Response
-
Within 5 days
you will receive progress updates from us at least every five working days.
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
5 assets you may test, 2 excluded.
Web 5
- https://www.xvideos.net/app Critical
- www.xnxx.com Critical
- www.xnxx.gold Critical
- www.xvideos.com Critical
- www.xvideos.red Critical
Out of scope (2)
- www.xvcams.com
- www.xvlivecams.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from XVIDEOS (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
Any vulnerability found must be reported no later than 24 hours after discovery.
-
You are not allowed to disclose details about the vulnerability anywhere else.
-
You must avoid tests that could cause degradation or interruption of our service.
-
You must not leak, manipulate, or destroy any user data.
-
You are only allowed to test against accounts you own yourself.
-
The use of automated tools or scripted testing is not allowed
-
Disclose the vulnerability report exclusively through HackerOne.
-
Network or simple Denial of Service attacks.
-
Automated tools or scans, botnet, compromised site, end-clients or any other means of large automated exploitation or use of a tool that generates a significant volume of traffic.
Not accepted
-
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
-
Account enumeration
-
Missing HTTP Headers
-
SSL/TLS best practices
-
Denial of Service and brute forcing attacks
-
Physical attacks against offices and data centers
-
Social engineering of our service desk, employees or contractors
-
Compromise of a Xvideos users or employees accounts
-
Use of a tool that generates a significant volume of traffic
-
Any hypothetical flaw or best practices without exploitable POC
-
Session timeout
-
Session Hijacking (cookie reuse)
-
Click-jacking
-
DKIM/SPF/DMARC issues
-
Information leakage, data cached in search engines or the web archive
-
Software version disclosure
-
HttpOnly, SameSite and Secure cookie flags
-
Downloading video
-
Confirmation Email (anything related with)
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 1 hour ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.
Original policy
Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Xvideos looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.
While we are doing our best to keep Xvideos services as safe as possible, we know that some bugs can slip through our scrutiny.
If you believe you've found a security issue in the services listed in our scope, we will work with you to resolve it promptly and ensure you are fairly rewarded for your discovery.
Scope
The scope of this program is limited to security vulnerabilities found on the Xvideos, Xvideos Red, Xnxx, and Xnxx Gold [as well as in the Xvideos and Xnxx Mobile application]. Vulnerabilities reported on other properties or applications are currently not eligible for monetary reward. High impact vulnerabilities outside of this scope might be considered on a case by case basis.
If you want to report a bug, without security or privacy issue, please fill the form here https://info.xvideos.com/contact
Domains
https://www.xvideos.com https://www.xvideos.red https://www.xnxx.com https://www.xnxx.gold https://www.xvideos.net/app/
Please note that cams.xvideos.com and cams.xnxx.com are not in the domain list, and not eligible for monetary reward. Please report bugs and security issues for cams domains here https://www.vsmedia.com/bugs/
Reward
Xvideos may provide rewards to eligible reporters of qualifying vulnerabilities. Rewards amounts vary depending upon the severity of the vulnerability reported.
Xvideos keeps the right to decide if the minimum severity threshold is met and whether the scope of the reported bug is actually already covered by a previously reported vulnerability. Rewards are granted entirely at the discretion of Xvideos. To qualify for a reward under this program, you should respect all the below criteria.
Eligibility and Responsible Disclosure
We are happy to work with everyone who submits valid reports which help us improve the security of Xvideos and Xnxx.
However, only those that meet the following eligibility requirements may receive a monetary reward:
- You need to be the first person to report an unknown issue
- Any vulnerability found must be reported no later than 24 hours after discovery.
- You are not allowed to disclose details about the vulnerability anywhere else.
- You must avoid tests that could cause degradation or interruption of our service.
- You must not leak, manipulate, or destroy any user data.
- You are only allowed to test against accounts you own yourself.
- The use of automated tools or scripted testing is not allowed
- You must not be a former or current Xvideos employee.
- Send a clear textual description of the report along with steps to reproduce the vulnerability, include attachments such as screenshots or proof of concept code as necessary.
- Disclose the vulnerability report exclusively through HackerOne.
Becareful, if your report requires the use of Burp Suite, there is a high chance that it is invalid. To avoid receiving a heavy penalty for a report classified as Invalid, please double-check multiple times that it is not a local hack (self-hack).
A good bug report should include the following information at a minimum:
- List the URL and any affected parameters
- Describe the browser, OS, and/or app version
- Describe the perceived impact. How could the bug potentially be exploited?
We intend to respond and resolve reported issues as quickly as possible. This means that you will receive progress updates from us at least every five working days.
Note that posting details or conversations about the report or posting details that reflect negatively on the program and the Xvideos / Xnxx brand, will result in immediate disqualification from the program.
Qualifying vulnerabilities
Please note that these are examples, and the list is non-exhaustive.
Vulnerabilities with a real security impact. Examples :
- Easy (zero to one click) user account takeover
- Backend interface takeover
- Server takeover (or potential takeover) Etc ...
The following are strictly prohibited:
- Network or simple Denial of Service attacks.
- Physical attacks against offices and data centers.
- Social engineering of our service desk, employees or contractors.
- Compromise of a Xvideos user's or employee's account.
- Automated tools or scans, botnet, compromised site, end-clients or any other means of large automated exploitation or use of a tool that generates a significant volume of traffic.
Non-qualifying vulnerabilities
This type of issues can be accepted if they lead to a serious data leak.
- Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
- Account enumeration
- Missing HTTP Headers
- SSL/TLS best practices
- Denial of Service and brute forcing attacks
- Physical attacks against offices and data centers
- Social engineering of our service desk, employees or contractors
- Compromise of a Xvideos users or employees accounts
- Use of a tool that generates a significant volume of traffic
- Any hypothetical flaw or best practices without exploitable POC
- Session timeout
- Session Hijacking (cookie reuse)
- Click-jacking
- DKIM/SPF/DMARC issues
- Information leakage, data cached in search engines or the web archive
- Software version disclosure
- HttpOnly, SameSite and Secure cookie flags
- Downloading video
- Confirmation Email (anything related with)