Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDiscover indexed invoice URL via search engine
-
DeliveryRequest PDF endpoint without authentication
-
ExploitRetrieve another customer's invoice
-
ExecutionEnumerate predictable invoice identifiers
-
ImpactHarvest PII and financial data at scale
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No special conditions beyond network reachability - remote unauthenticated exploitation (PR:N/UI:N) against Copart's Online Billing Service, specifically the endpoint that serves PDF invoice files, which performs no authorization check before returning documents. Exploitation is further eased because some invoice document URLs are publicly indexed by search engines and because invoice identifiers are predictable, allowing enumeration. The practical limiting factor is that exploitation targets a single vendor-hosted web application rather than on-premises software, so impact is confined to Copart's billing customers and depends on the current (possibly already remediated) state of that hosted service. |
| Impact | The CVSS 4.0 base score of 9.2 (Critical) is driven by a fully remote, unauthenticated, low-complexity vector (AV:N/AC:L/AT:N/PR:N/UI:N) with high confidentiality impact on both the vulnerable system (VC:H) and a subsequent system (SC:H), reflecting broad PII/financial data exposure. However, the technical-impact signal is confidentiality-only (VI:N/VA:N, SI:N/SA:N) - there is no integrity or availability impact, so this is a pure data-exposure flaw rather than a system-takeover issue. No EPSS score, CISA KEV listing, POC reference, or SSVC decision data was provided in the input, so exploitation likelihood cannot be quantified from threat-intel signals; the only exploitation enabler noted is that some invoice URLs are reportedly indexed by search engines, which materially lowers the effort to discover exposed documents. The disclosure originates from INCIBE (Spain's CERT), a credible national coordinator, which supports the validity of the finding, but there is no vendor advisory or fix version in the provided data. Net assessment: a genuinely high-severity confidentiality issue for affected Copart customers because exploitation is trivial and may already be partially achievable via search engines, but the absence of EPSS/KEV/POC data means the 9.2 should be treated as severity-of-impact rather than confirmed widespread exploitation - verify current exposure and indexing status directly. |
| Exploit ScenarioDerived | An unauthenticated attacker browses or guesses the PDF-invoice endpoint URL, which lacks authorization checks, and retrieves invoices belonging to other customers containing names, addresses, invoice numbers, payment details, and tax information. Because invoice identifiers appear predictable, the attacker increments or enumerates IDs to harvest additional customers' documents at scale; some URLs are already reachable through search-engine indexing, so no credentials or prior access are required. No public POC was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Remote unauthenticated attackers can retrieve confidential PDF invoices from Copart's Online Billing Service because the endpoint that serves those documents performs no authorization check, exposing customer names, addresses, invoice numbers, payment details and tax information. Exploitation is made easier by invoice document URLs that are publicly indexed by search engines and by predictable invoice identifiers, which allow an attacker to enumerate and pull additional files beyond any single leaked link. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, but the CVSS 4.0 base score of 9.2 (Critical) reflects a fully remote, low-complexity, unauthenticated vector with high confidentiality impact on both the vulnerable service and a subsequent system.
RemediationAI
This vulnerability affects a vendor-operated hosted service, so no client-side patch exists - remediation must be performed by Copart on the invoicing platform itself. The required fix is server-side authorization enforcement on the PDF invoice endpoint: every request must be tied to an authenticated session and validated against the requesting account's ownership of the referenced invoice, returning 403/404 rather than the document otherwise. Because no vendor-released patch or fix version is identified in the available data, the practical near-term controls are those available to the service owner and its customers. For Copart, the strongest compensating measure is replacing predictable, sequential invoice identifiers with long random or signed tokens such as UUIDv4 or HMAC-signed URLs, which removes the enumeration primitive; the trade-off is that previously bookmarked or shared invoice links and any downstream integrations that construct URLs from invoice numbers will break and must be updated. Adding authentication and per-object ownership checks to the document handler entails session-management overhead and may complicate automated invoice delivery, but it is the only control that fully closes the exposure. Publishing robots.txt disallow rules or X-Robots-Tag: noindex headers can reduce further indexing of invoice paths by search engines, but this only limits discovery and does not prevent direct access, and cached search-engine copies persist after the rules are added. Blocking or rate-limiting direct access to the PDF path from unauthenticated clients provides temporary friction that attackers can bypass by mimicking legitimate traffic, and it can break legitimate customer downloads. Copart should also audit historical access logs for bulk or sequential invoice-path requests to determine whether the disclosure was actually exercised, and affected customers should be notified so they can watch for fraud using the exposed names, addresses, payment details and tax information. Until the vendor confirms a fix, individuals whose invoices may have been exposed should treat that data as compromised for phishing and identity-theft purposes. The INCIBE notice at https://www.incibe.es/en/incibe-cert/notices/aviso/unauthorised-disclosure-information-coparts-online-billing-service is the reference point for vendor status updates.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is an instance of CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) rooted in missing server-side authorization on the document-serving component of Copart's customer invoicing web application. Functionally this is a broken object-level authorization / insecure direct object reference pattern: the HTTP handler that streams generated PDF invoices returns the file without verifying that the requester is authenticated or owns the referenced invoice. Because the PDF identifiers are predictable, an attacker can iterate or guess them rather than needing a leaked link, and because some invoice URLs have been crawled and indexed by search engines, valid document paths are discoverable without any prior knowledge of the system. The CPE cpe:2.3:a:copart:copart’s_online_billing_service carries no version granularity because this is a vendor-hosted web application rather than distributable software, so the vulnerable artifact is the live service code path, not a shipped release. The CVSS 4.0 vector AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N indicates no integrity or availability impact at all - the entire risk is confidentiality loss, with subsequent-system impact (SC:H) implying that data reachable through the same platform extends beyond the directly requested invoice. The independent assessment's CVSS 3.1 equivalent (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N) agrees on scope change and total confidentiality compromise with no other impact class.
Know when Copart S Online Billing Service gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
Remote unauthenticated access to an authorization-free endpoint gives AV:N/AC:L/PR:N/UI:N; exposed customer data sits in a separate security authority so S:C with C:H, and no integrity/availability impact (I:N/A:N).
Primary rating from Vendor (INCIBE).
CVSS VectorVendor: INCIBE
Lifecycle Timeline
2DescriptionCVE.org
A vulnerability relating to the exposure of confidential information in the customer invoicing web application, which exposes personally identifiable information (PII) and financial data - including customer names, addresses, invoice numbers, payment details and tax information - to unauthorised individuals. The issue is caused by a lack of authorisation checks at the endpoint responsible for serving PDF invoice files. Furthermore, some URLs for invoicing documents appear to be publicly accessible via search engines, exposing paths to confidential files. Successful exploitation of this vulnerability could allow an attacker to access data to which they should not have access, as well as to predict identifiers in order to access even more confidential information.
Executive ViewAI
Copart's Online Billing Service is exposing confidential customer invoices - including names, addresses, payment details and tax identifiers - to anyone who can reach the document endpoint, because those files are served without any authorization check and are further discoverable through search engine indexing and guessable invoice identifiers. Because the exposure is embedded in customer-facing billing infrastructure and no vendor fix is currently available, the organization faces regulatory notification obligations, customer trust damage and potential contract or audit exposure across every billing account whose invoices can be enumerated. Leadership should treat this as an active data-exposure condition rather than a pending patch item, since the risk grows with each additional document an outside party retrieves.
No vendor-released patch identified at time of analysis. Interim mitigations: enforce an authorization check in front of the document endpoint (reverse proxy, WAF or gateway) that denies unauthenticated or non-owning requests; disable search engine indexing and request removal of already-indexed invoice URLs; replace predictable invoice identifiers with unguessable tokens; apply rate limiting and volume-based blocking on the document path; alert on sequential or bulk invoice retrieval patterns in access logs; and preserve logs for breach-notification assessment.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-100940
GHSA-cvj8-qjr2-gmp7
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB