Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

SoSci Survey GmbH

Bug bounty on security.txt soscisurvey.de

Accepting reports Full safe harbor KYC to get paid security.txt
Go to program Website
Top reward
€250
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.

Pays up to €250
top reward, from €25.
Report by email
[email protected]
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 5 days
As the policy promises.
Paid by bank transfer, PayPal
Proof of identity needed to get paid.
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.

Top reward
€250 bounties typically range from 25 € to 250 €
Lowest reward
€25 bounties typically range from 25 € to 250 €
Response
Within 5 days We will acknowledge receipt of your report within 5 working days.
Safe harbor
Full If you act in good faith and within the rules on this page, we consider your research to be authorized by us. In this case, we will not take legal action against you or file a criminal complaint.
Hall of fame
Yes If you wish, we will credit you in the release notes as the person who discovered the vulnerability.

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

Domains 2

  • soscisurvey.de
  • www.soscisurvey.de
Out of scope (2)
  • s2survey.net
  • support.soscisurvey.de

Rules

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

While testing

  • Only test with your own accounts and test projects. Other users' projects, data, and participants are off-limits.
  • If you nevertheless gain access to other people's data, stop testing immediately, access only as much as necessary to prove the issue, report the finding to us right away, and delete any data you may have retrieved.
  • Do not send emails or invitations from test projects to people who have not consented.
  • Do not carry out denial-of-service attacks or place excessive load on our servers. Automated tools must not send more than 5 requests per second.
  • Social engineering, phishing, and physical attacks are not permitted.
  • Do not modify or delete data that does not belong to you, and do not install persistent backdoors.

Not accepted

  • missing or optional security mechanisms without demonstrated impact, e.g., HTTP security headers, MTA-STS, CAA, SPF, or DMARC records
  • clickjacking on pages without security-relevant actions
  • self-XSS
  • disclosure of software or plugin versions without a demonstrated vulnerability
  • attacks that require an already compromised device or browser
  • output from automated scanners without verification and proof

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.