- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 6
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays cash
- Amounts are not published; ask before you invest time.
- Report by email
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 5 days
- As the policy promises.
- Paid by PayPal
- Proof of identity needed to get paid.
Rewards
What the company's own policy page says it pays.
The policy page has no reward table. Here is what it says, in its own words.
- Lowest reward
-
$100
LOW | [100, 249]
- Pays cash
-
Yes
We will ask you for your paypal email, so we can make a transfer to your account.
- Response
-
Within 5 days
We will take at most 5 business days since email reception to triage your report.
- Safe harbor
-
Full
we will not take legal actions against you nor ask law enforcement to investigate you as long as you abide by these general rules
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
6 assets you may test, 2 excluded.
Domains 6
- fintu.al
- fintual.cl
- fintual.com
- fintual.in
- fintual.mx
- fnt.al
Out of scope (2)
- fintualist.com
- store.fintual.cl
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Fintual's policy. "We" in these lines means the program, not this site.
While testing
-
do not leak our information
-
do neither modify nor delete our data
-
do not degrade our service
-
Use only accounts you own.
-
If you use an active account belonging to one of our clients, you must obtain their explicit permission before using it
Not accepted
-
Rate limiting non-sensitive endpoints
-
Best practices concerns without evidence of a real security vulnerability
-
Race conditions that don't compromise the security of our users, employees or business
-
Reports about theoretical damage without a real risk
-
The output of automated scanners without explanation and evidence of a security vulnerability
-
Missing cookie flags on non-security sensitive cookies
-
Attacks requiring physical or console access to a user's device
-
Missing security headers not related to a security vulnerability
-
Reports of insecure SSL/TLS ciphers unless you have a working proof of concept
-
Open ports without a vulnerability
-
Disclosure of known public files or directories, (e.g. robots.txt)
-
DNSSEC and DANE
-
HSTS or CSP headers
-
Host header injection without showing how a third-party can exploit it
-
Firebase `apiKey` in our websites (read their documentation!)
-
Missing DMARC/BIMI
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.