- Top reward
- Not published
- 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.
- 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.
- Publish after a fix
- Coordinate the timing with the company.
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.
- Pays cash
-
Yes
The only monetary reward exceptions are the specific assets listed in our Public Bug Bounty Program on Intigriti.
- Safe harbor
-
Full
When conducting vulnerability research according to this policy, we consider this research to be authorized, lawful, helpful to the overall security of the Internet, and conducted in good faith.
- Hall of fame
-
Yes
Visma Security Hall of Fame
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.
Products and areas 1
- all Visma services, products or web properties
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Visma's policy. "We" in these lines means the program, not this site.
While testing
-
Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope.
-
Only interact with accounts or devices you own or with explicit permission from the owner.
-
Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
-
If a vulnerability provides unintended access to data, limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept.
-
Cease testing and submit a report immediately if you encounter any user data during testing, such as personal data and sensitive personal data, credit card data, or proprietary information.
-
Do not attempt to execute Denial of Service attacks.
-
Social engineering (e.g. phishing, vishing, smishing) is prohibited.
-
Do not engage in extortion by demanding a reward before disclosing vulnerability details.
-
Use only the official channels to discuss vulnerability information with us.
Not accepted
-
Theoretical vulnerabilities without any proof or demonstration of the real presence of the vulnerability.
-
Findings from automated tools without providing a Proof of Concept.
-
Missing or weak security-related HTTP headers.
-
Non-Sensitive Data Disclosure, for example server version banners.
-
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS.
-
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions.
-
Self-XSS.
-
Missing email best practices (invalid, incomplete or missing SPF/DKIM/DMARC records, etc.).
-
Host header injection, unless you have confirmed that it can be exploited in a practical attack.
-
Expired SSL certificates, weak SSL Ciphers, or issues regarding old TLS/SSL versions.
-
Previously known vulnerable software or libraries without a working Proof of Concept.
-
Rate limiting or bruteforce issues on non-authentication endpoints.
-
Denial of Service.
-
CSV/formula injection.
-
Flash based exploits.
-
Clickjacking.
-
Google Maps API key disclosure.
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.