Skip to content

Tuxis

Vulnerability disclosure program on security.txt tuxis.nl

Accepting reports Full safe harbor security.txt expired
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
2
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.
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 1 day
As the policy promises.
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.

Response
Within 1 days We will send you a confirmation of receipt within one working day.
Safe harbor
Full If you make the report according to the procedure, we have no reason to attach legal consequences for your report.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

2 assets you may test.

Domains 2

  • tuxis.cloud
  • tuxis.nl

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Tuxis's policy. "We" in these lines means the program, not this site.

While testing

  • Report it as soon as possible after discovering the vulnerability.
  • Do not share the information about the security problem with others until you hear from us whether it has been resolved.
  • You use the knowledge of the security problem responsibly, for example, by not taking any action that goes beyond what is necessary to prove the security problem.
  • Placing malware.
  • Copying, changing or deleting data in a system.
  • Making changes to the system.
  • Repeatedly accessing the system or sharing access with others.
  • Using brute force to gain access to a system.
  • Using denial-of-service or social engineering.

Not accepted

  • An anomaly that has no impact on the availability, integrity or confidentiality of information.
  • The availability of WordPress xmlrpc.php and alike functionality when its misuse is limited to a so-called ping-back denial-of-service.
  • The possibility of cross-site scripting on a static website or on a website on which no sensitive (user) information is processed.
  • The availability of version information via, for instance, an info.php file.

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 12 Nov 2026. Last checked 3 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.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.