Skip to content

JD Services

By JD Services B2B OÜ Bug bounty on Self-hosted jd-services.eu

Accepting reports Full safe harbor KYC to get paid security.txt
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 PayPal, SEPA bank transfer
Proof of identity needed to get paid.
No public write-ups
Keep findings private.

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 for critical vulnerabilities, we might also provide a discretional bounty payment through PayPal or SEPA bank transfer (issurance of legal invoice and signed agreement would be required)
Response
Within 3 days although we might take up to 72 hours to provide an email response to your report.
Safe harbor
Full we consider this research conducted under this policy to be: authorized concerning any applicable anti-hacking laws
Hall of fame
Yes we will be providing public credit to researchers who discovered them in our Wall of Fame below

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, 1 excluded.

Products and areas 1

  • any digital assets owned, operated, or maintained by JD Services B2B OÜ
Out of scope (1)
  • Our customers systems and practices

Rules

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

While testing

  • play by the rules, including following this policy and any other relevant agreements
  • report any vulnerability you’ve discovered promptly
  • avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience
  • use only the Official Channels to discuss vulnerability information with us
  • perform testing only on in-scope systems, and respect systems and activities which are out-of-scope
  • you should only interact with test accounts you own, and not use or access accounts owned by third parties
  • do not engage in extortion
  • limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept

Not accepted

  • mere potential security improvements

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.