Skip to content

Accodeing

Bug bounty on Self-hosted accodeing.com

Accepting reports Full safe harbor
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.
Replies within 3 days
As the policy promises.
Paid by invoice, gift certificate
No identity requirement stated.
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.

Lowest reward
€20 The minimum reward will be €20.
Pays cash
Yes As a token of our gratitude for your assistance, we offer a reward for every report of a security problem that was not yet known to us.
Response
Within 3 days We will respond to your report within 3 business days with our evaluation of the report and an expected resolution date if you have followed the instructions above and we judge the report to be valid,
Safe harbor
Full If you have followed the instructions above, we will not take any legal action against you in regard to the report,
Hall of fame
Yes In the public information concerning the problem reported, we will give your name as the discoverer of the problem (unless you desire otherwise), and

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.

Domains 1

  • accodeing.com

Rules

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

While testing

  • E-mail your findings to [email protected].
  • Encrypt your findings using our PGP key to prevent this critical information from falling into the wrong hands.
  • Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people’s data,
  • Do not reveal the problem to others until it has been resolved,
  • Do not use attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties, and
  • Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible.

Not accepted

  • Results from automated tools or scans, missing security headers, missing security best practices, or reports indicating that the software is out of date.

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.

Search NVD

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