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

Cox Automotive

Vulnerability disclosure program on security.txt coxautoinc.com

Accepting reports security.txt
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
9
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report by email
[email protected]
Partial safe harbor
Some legal protection; read the terms.
Replies within 2 days
As the policy promises.
No public write-ups
Keep findings private.

Rewards

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

This program does not pay cash rewards.

Pays cash
No Cox Automotive does not offer a bounty program or provide compensation in exchange for security vulnerability submissions at this time.
Response
Within 2 days The Cox Automotive Security team will acknowledge receipt of each vulnerability report within two (2) business days
Safe harbor
Partial When conducting vulnerability research within the terms of this policy, we consider such research to be: Lawful, helpful to and supportive of Cox Automotive’s Cybersecurity posture, and conducted in good faith. However: Misuse of Cox Automotive systems may result in personal civil and/or criminal li

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

Scope

9 assets you may test, 3 excluded.

Domains 6

  • centraldispatch.com
  • coxautoinc.com
  • dealer.com
  • vauto.com
  • vinsolutions.com
  • xtime.com

APIs 1

  • APIs

Products and areas 2

  • Cox Automotive web properties
  • other applications
Out of scope (3)
  • Cox Automotive customers
  • Cox Automotive employees and contractors
  • physical security

Rules

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

While testing

  • Contact us immediately before you access anyone else’s data, personal or otherwise.
  • You must report the vulnerability to us with no conditions attached.
  • You must stop after you find the first vulnerability and request permission to continue testing.
  • Perform any tests that will disrupt services or impair others’ ability to use them.
  • Exfiltrate data – instead use a proof of concept to demonstrate a vulnerability
  • Execute any testing that may add, modify, update, or delete existing data
  • Perform social engineering or phishing against Cox Automotive employees and contractors
  • Publicly disclose any vulnerabilities without explicit written permission from Cox Automotive
  • Attempt to brute force passwords
  • Use automated scanners

Not accepted

  • Any bug that does not pose a substantial or demonstrable security risk
  • Clickjacking, open redirects, or lack of security headers
  • Denial of Service (DOS)
  • Social engineering
  • Physical exploits of our servers or network
  • Local network-based exploits such as DNS poisoning or ARP spoofing
  • Cross Site Scripting blocked by browser features in Edge, Firefox, Chrome and Safari
  • Vulnerabilities remediated by known vendor patches
  • Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
  • Information disclosure without demonstratable impact
  • Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
  • Missing best practices in Content Security Policy
  • Missing HttpOnly or Secure flags on cookies
  • Vulnerabilities only affecting users of outdated or unpatched browsers
  • Open redirect – unless an additional security impact can be demonstrated
  • Clickjacking on non-sensitive action pages
  • Missing best practices in SSL/TLS configuration

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.