CarsideMirrors · Bug bounty Australia

Bug bounty programfor security researchers

Hunting for a paid bug bounty in Australia? Our responsible disclosure program rewards valid XSS, CSRF, access-control and auth findings with A$50–A$1,000 — plus optional Hall of Fame recognition.

Also listed on Open Bug Bounty · OZ Automotives program

Clear AUD rewards

Published tiers from A$50 to A$1,000 — no guesswork on payout ranges.

Modern attack surface

Next.js storefront, API, admin auth, checkout/Stripe, and status — real ecommerce targets.

Hall of Fame credit

Valid researchers can be listed with points, bounty, and LinkedIn or X links.

Bounty ranges

Bug bounty rewards from A$50 to A$1,000

Paid in Australian dollars for eligible responsible disclosure. Final amounts reflect severity, PoC quality, and real-world impact on CarsideMirrors.

Low

A$50–A$150

Low-impact disclosure, non-sensitive misconfiguration.

Medium

A$150–A$400

Limited privilege issues, CSRF on important actions.

High

A$400–A$700

Stored XSS, IDOR on customer data, constrained auth bypass.

Critical

A$700–A$1,000

RCE, account takeover, checkout abuse, mass PII exposure.

How it works

From vulnerability report to reward

  1. 01

    Report

    Send a clear PoC with steps, impact, CVSS if possible, and the affected URL or endpoint.

  2. 02

    Triage

    We acknowledge valid reports and assess severity and business impact.

  3. 03

    Remediate

    We prioritise a fix and keep you updated where appropriate.

  4. 04

    Reward

    Eligible findings are paid in AUD and may appear on our Hall of Fame.

Program scope

In-scope hosts for ethical hacking

Focus testing on these CarsideMirrors surfaces. Stay within scope so your bug bounty submission stays eligible.

In scope

  • ozcarsidemirrors.comStorefront & checkout
  • api.ozcarsidemirrors.comPublic & authenticated APIs
  • admin.ozcarsidemirrors.comAuth issues only — no brute force
  • status.ozcarsidemirrors.comPublic status surface

Out of scope

  • Denial of service or resource exhaustion
  • Social engineering, phishing, or physical attacks
  • Scanner noise without a working proof of concept
  • Third-party platforms we do not control (unless our misconfiguration)
  • Missing headers with no demonstrated security impact

Ground rules

Research safely and ethically

We welcome skilled security researchers. Follow these rules so we can protect customers and reward your work fairly.

  1. 01

    Test only assets listed in scope, in good faith.

  2. 02

    Do not access or destroy real customer data — use your own test accounts.

  3. 03

    No public disclosure until we confirm a fix or grant written permission.

  4. 04

    One bounty per unique issue; first valid report wins.

  5. 05

    Awards are discretionary and based on severity, quality, and impact.

Submit your finding

Report a vulnerability

Send a detailed bug bounty report with reproduction steps, impact, and severity. Our team reviews every valid submission and replies by email.

  • Working PoC, affected URL, and impact summary
  • Severity helps us triage faster
  • Eligible reports earn A$50–A$1,000 AUD

Vulnerability report

Submit a finding

Provide enough detail for us to reproduce the issue. Fields marked required must be completed.

Researcher details
Severity *

Select the severity that best matches your finding. Final reward is decided during triage.

Vulnerability details
Security check *

What is …?

FAQ

Bug bounty FAQ

Answers for security researchers evaluating the CarsideMirrors vulnerability reward program before testing.

Is this a paid bug bounty program in Australia?

Yes. CarsideMirrors by OZ Automotive runs a paid bug bounty / responsible disclosure program. Valid in-scope findings are rewarded in Australian dollars from A$50 to A$1,000 depending on severity and report quality.

What vulnerabilities are in scope for the bounty?

We welcome XSS, CSRF, open redirects, improper access control, IDOR, authentication issues, and similar web application flaws on the listed hosts. Intrusive testing such as destructive SQL injection should be reported privately with a minimal PoC — do not exploit customer data.

How do security researchers get paid?

Eligible reports are paid in AUD after triage and remediation. Payment details are arranged by email with the researcher. Recognition may also appear on our public Hall of Fame.

Can I disclose findings publicly?

Not until we confirm a fix or give written permission. Premature disclosure makes a report ineligible for a bounty. Coordinated disclosure protects customers and preserves your reward.

Chat with us