iFixit
Vulnerability disclosure program on Self-hosted ifixit.com
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 1
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report by email
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 3 days
- As the policy promises.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Response
-
Within 3 days
We aim to respond within 3 business days, however some reports take longer than others to investigate.
- Safe harbor
-
Full
We won't take legal or administrative action against you or your account if you act accordingly: White hat researchers are always appreciated.
- Hall of fame
-
Yes
Here are people who have responsibly disclosed verified vulnerabilities in the past:
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
1 asset you may test, 1 excluded.
Domains 1
- ifixit.com
Out of scope (1)
- createsend.ifixit.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from iFixit's policy. "We" in these lines means the program, not this site.
While testing
-
Please act in good faith towards our users' privacy and data during your disclosure.
-
When testing for vulnerabilities, please do not insert test code into popular public guides or threads .
-
Please, always make a new guide or ask a new question instead!
-
If those actions are not possible, please delete all guides, comments, and posts when you have completed your testing and reporting.
Not accepted
-
Outdated versions of Wordpress with no known vulnerabilities
-
Username enumeration
-
Self-XSS
-
Missing DNS SPF records
-
Security problems with subdomains such as createsend.ifixit.com that are operated by third party services
-
Password policy “best practice” recommendations
-
Lack of email verification
-
Vulnerabilities which require preexisting privileged access to user data (e.g. session cookies, leaked passwords, etc.).
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 5 hours 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.