Skip to content

Adevinta

Vulnerability disclosure program on HackerOne adevinta.com

Accepting reports
Top reward
No cash rewards
Top severity paid
Critical
Assets in scope
19
Public CVEs
0
Last change

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report on HackerOne
Submit through the program page.
No public write-ups
Keep findings private.

Rewards

What HackerOne lists as the payout for each severity.

This program does not pay cash rewards.

Scope

19 assets you may test.

Web 19

  • 2dehands.be Critical No bounty
  • 2ememain.be Critical No bounty
  • adevinta.com Critical No bounty
  • infojobs.it Critical No bounty
  • jobmarketinsights.com Critical No bounty
  • kijijiautos.ca Critical No bounty
  • kijiji.ca Critical No bounty
  • marktplaats.nl Critical No bounty
  • motos.net Critical No bounty
  • multigestionale.com Critical No bounty
  • nostromo.epreselec.com Critical No bounty
  • null-leasing.com Critical No bounty
  • subito.it Critical No bounty
  • www.automobile.it Critical No bounty
  • www.coches.net Critical No bounty
  • www.infojobs.net Critical No bounty
  • www.kleinanzeigen.de Critical No bounty
  • www.milanuncios.com Critical No bounty
  • www.mobile.de Critical No bounty

Rules

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

While testing

  • Please provide detailed reports with reproducible steps.
  • Submit one vulnerability per report unless you need to chain vulnerabilities to provide impact.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
  • Only interact with accounts you own or with explicit permission of the account holder.
  • Please do not interact with other users. If you need to test user interactions please use test accounts under your control.

Not accepted

  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • No DoS/DDoS testing.
  • Submitting contact forms in which the researcher is not in control of both the sender and the recipient of the contact form.

Summarised with AI from the program policy on HackerOne, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 1 hour ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Before we tracked it

Scope and reward changes recorded before this page started tracking it.

  1. Scope removed

    www.fotocasa.es

  2. Scope removed

    fotocasa.pro

  3. Scope removed

    datavenues.com

  4. Scope removed

    habitaclia.com

  5. Scope added

    2dehands.be

  6. Scope added

    2ememain.be

  7. Scope added

    adevinta.com

  8. Scope added

    infojobs.it

  9. Scope added

    jobmarketinsights.com

  10. Scope added

    kijiji.ca

  11. Scope added

    kijijiautos.ca

  12. Scope added

    marktplaats.nl

  13. Scope added

    motos.net

  14. Scope added

    multigestionale.com

  15. Scope added

    nostromo.epreselec.com

  16. Scope added

    null-leasing.com

  17. Scope added

    subito.it

  18. Scope added

    www.automobile.it

  19. Scope added

    www.coches.net

  20. Scope added

    www.infojobs.net

  21. Scope added

    www.kleinanzeigen.de

  22. Scope added

    www.milanuncios.com

  23. Scope added

    www.mobile.de

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.

Original policy

Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Disclosure Policy

  • Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
  • Follow HackerOne's disclosure guidelines.

Program Rules

  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged.
  • Submit one vulnerability per report unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur, we only triage the first report received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.
  • Some of the assets in scope may be mirror sites for the most part, duplicated vulnerabilities will be grouped.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • No DoS/DDoS testing.
  • Submitting contact forms in which the researcher is not in control of both the sender and the recipient of the contact form.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
  • Only interact with accounts you own or with explicit permission of the account holder.
  • If you need to create public content, for example ads or public profile, please don't draw attention with the content.
  • Please do not interact with other users. If you need to test user interactions please use test accounts under your control.
  • Moving beyond “proof of concept” report steps (for example: proving that account takeover vulnerability with a dummy test account is acceptable, but not exploiting or accessing customer accounts)
  • We've got the automated vulnerability scanners under control, thanks! Right now, what we really need is your brainpower, not just raw processing power. While automated tools are handy, we're looking for a bit more depth in the analysis. So, if you come across vulnerabilities, it would be awesome if you could provide some additional insights into why they're a concern.

Session Layer: HTTP Headers

Researchers should add headers to requests such as:

  • “X-HackerOne-Research: [H1 username]”

Thank you for helping keep Adevinta and our users safe!