Skip to content

UXCam

Bug bounty on security.txt uxcam.com

Accepting reports Full safe harbor security.txt mentions bounty
Top reward
$1,000
Top severity paid
Critical
Assets in scope
13
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

Pays up to $1,000
for critical bugs, from $50.
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 5 days
As the policy promises.
Paid by PayPal, bank transfer
No identity requirement stated.
No public write-ups
Keep findings private.

Rewards

What the company's own policy page says it pays.

Severity Reward
Critical $1,000 from $650
High $650 from $300
Medium $300 from $150
Low $150 from $50
Top reward
$1,000 Maximum reward $1000
Lowest reward
$50 Minimum reward $50
Response
Within 5 days Allow us to respond to you within 5 business days with our evaluation of your report and the expected resolution date.
Safe harbor
Full We will not take any legal action against you if you play by the rules.
Hall of fame
Yes To be eligible for the Hall of Fame , researchers must submit report for valid and impactful vulnerabilities.

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

Scope

13 assets you may test, 12 excluded.

Domains 5

  • app.uxcam.com
  • dashboard.uxcam.com
  • uxc.am
  • uxcam.com
  • uxcam-storage.com

Source code 3

  • github.com
  • https://github.com/uxcam
  • Public SDK repos in our GitHub organization ( github.com/uxcam)

Wildcard domains 3

  • *.uxc.am
  • *.uxcam.com
  • *.uxcam-storage.com

Products and areas 2

  • Latest version of our SDKs
  • Mobile/Web SDKs
Out of scope (12)
  • bug-bounty.uxcam.com
  • connect.uxcam.com
  • developer.uxcam.com
  • help.uxcam.com
  • help.uxcam.com/en
  • info.uxcam.com
  • resources.uxcam.com
  • sdk.uxcam.com
  • status.uxcam.com
  • tara.uxcam.com
  • trust.uxcam.com
  • uxcam.com/resources

Rules

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

While testing

  • Do not attempt to access or modify another user’s data or account. For any cross-account testing, use only your own test accounts.
  • Avoid actions that may impact service integrity, availability, or confidentiality. Prohibited actions include DDoS, spam, or other disruptive testing.
  • Testing must not affect real users or lead to unauthorized data changes or service interruptions.
  • Test only on targets explicitly listed in the program scope, and ensure you are interacting only with assets owned and operated by UXCam.
  • Automated tools may be used if rate-limited to a maximum of 5 requests per second ; excessive traffic may result in IP or account bans.
  • Do not attempt any social engineering attacks, including phishing or pretexting against UXCam employees or users.
  • If you accidentally access or believe that you have accessed sensitive data of customers, employees, or of UXCam, stop testing immediately, securely delete the data, and report it promptly to us.
  • Do not share, disclose, or discuss any vulnerabilities outside of UXCam’s security team or the program’s submission process.
  • Name field: Add this string to your name/organization name: BugBounty-
  • Please include the following header in all server requests; this allows us to identify researcher testing activity and avoids blocking: X-User-Id: <email_you_used_for_bugbounty_signup>

Not accepted

  • All P5 vulnerabilities corresponding to Bugcrowd's VRT .
  • Any findings related to data breaches which are within the public domain.
  • Banner disclosures on common/public services.
  • Missing best practices (e.g. Content Security Policy, Anti-MIME-Sniffing headers).
  • TLS/SSL-related concerns (e.g. forward secrecy, insecure cipher suites) without proof of exploitability.
  • OPTIONS / TRACE HTTP methods enabled.
  • Email spoofing due to misconfigured SPF/DKIM/DMARC records.
  • Spam-related reports (SMS, email, etc.).
  • Username/email enumeration via Login/Forgot Password page error messages.
  • Lack of rate limiting or brute force issues.
  • Weak CAPTCHA / CAPTCHA bypass issues.
  • Logout Cross-Site Request Forgery (logout CSRF).
  • Clickjacking/tapjacking without significant security impact.
  • Missing HTTP security headers.
  • CSRF on non-sensitive forms accessible to anonymous users (e.g. the demo request form).
  • Known vulnerabilities in libraries or out-of-date software without known exploits.
  • Vulnerabilities limited to unsupported browsers.
  • Reports directly from automated tools or scans without a manual PoC.
  • Denial of Service (DoS/DDoS) attacks.
  • Files without sensitive information.
  • Cross-Site Request Forgery (CSRF).
  • SDK occlusion/masking or opt-out/consent gaps that don't expose data to an unauthorized party.
  • Privacy or regulatory-compliance concerns (e.g. GDPR) without a demonstrated security vulnerability.

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 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.