Fluxer
Vulnerability disclosure program on Self-hosted fluxer.app
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 20
- 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.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Pays cash
-
No
It isn't a bug bounty program and has no set rewards.
- Safe harbor
-
Full
Research done in good faith under this policy is authorized for the purposes of Swedish, EU, US and equivalent anti-hacking laws. We won't take legal action against you for it, and we'll confirm that it was authorized if a third party challenges it.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
20 assets you may test, 7 excluded.
Domains 10
- fluxer.app
- fluxerapp.com
- fluxer.com
- fluxer.dev
- fluxer.gg
- fluxer.gift
- fluxer.media
- fluxerstatic.com
- fluxer.tools
- fluxerusercontent.com
Wildcard domains 9
- all of their subdomains
- *.fluxer.app
- *.fluxerapp.com
- *.fluxer.dev
- *.fluxer.gg
- *.fluxer.gift
- *.fluxer.media
- *.fluxerstatic.com
- *.fluxerusercontent.com
Products and areas 1
- supported self-hosted releases
Out of scope (7)
- feature requests
- ordinary UI bugs
- phishing
- physical attacks
- social engineering
- Third-party systems we don't control
- unsupported instances
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Fluxer's policy. "We" in these lines means the program, not this site.
While testing
-
Don't run denial-of-service testing, noisy scanning, flooding, brute-force attempts or resource exhaustion.
-
Test only with accounts, communities, systems and data you own or have permission to use.
-
Don't access, change, keep or delete data that belongs to someone else.
-
Don't message users outside your test, scrape data, evade safeguards in bulk or trigger real billing, payments or notifications without asking us first.
-
Use minimal access to prove impact, and delete personal data from tests once it's no longer needed.
-
Keep the report private until we've confirmed and fixed the issue, which typically takes up to 90 days.
-
If you're not sure whether a test is in scope, ask first.
Not accepted
-
best-practice observations without a credible security impact
-
physical attacks
-
social engineering
-
phishing
-
ordinary UI bugs
-
feature requests
-
unsupported instances
-
a theoretical issue with no realistic attack path
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 6 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.