CVE-2026-71242
Crater: Cross-Company IDOR on Notes via Missing Company-Ownership Check in NotePolicy
Description
Crater's NotePolicy checks only a blanket Bouncer ability (manage-all-notes / view-all-notes) with no company-ownership comparison, unlike InvoicePolicy and other sibling policies which additionally verify $user->hasCompany($model->company_id). NotesController's show(), update(), and destroy() actions authorize via $this->authorize('view notes'/'manage notes') without passing the target Note model, and Note's company-scoping (scopeWhereCompany) is applied only in the list endpoint, not in show/update/destroy. Any authenticated user of one company can read, edit, or delete another company's notes by ID. This is a distinct finding from the previously reported CustomerPolicy company-ownership omission (a different policy class and controller).
INFO
Published Date :
Aug. 5, 2026, 11:16 a.m.
Last Modified :
Aug. 5, 2026, 1:24 p.m.
Remotely Exploit :
Yes !
Source :
309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c
Affected Products
The following products are affected by CVE-2026-71242
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | |||||
| CVSS 3.1 | HIGH | 309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c | ||||
| CVSS 3.1 | HIGH | MITRE-CVE |
Solution
- Add company-ownership check to NotePolicy.
- Pass Note model to authorize() in NoteController.
- Apply company-scoping to show/update/destroy actions.
- Review all policies for similar omissions.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-71242.
| URL | Resource |
|---|---|
| https://github.com/crater-invoice/crater |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-71242 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-71242
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-71242 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-71242 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c
Aug. 05, 2026
Action Type Old Value New Value Added Affected [{'vendor': 'crater-invoice', 'product': 'crater', 'versions': [{'status': 'affected', 'version': '6.0.6'}], 'programFiles': ['app/Policies/NotePolicy.php', 'app/Http/Controllers/V1/Admin/General/NotesController.php'], 'defaultStatus': 'unknown'}] Added Description Crater's NotePolicy checks only a blanket Bouncer ability (manage-all-notes / view-all-notes) with no company-ownership comparison, unlike InvoicePolicy and other sibling policies which additionally verify $user->hasCompany($model->company_id). NotesController's show(), update(), and destroy() actions authorize via $this->authorize('view notes'/'manage notes') without passing the target Note model, and Note's company-scoping (scopeWhereCompany) is applied only in the list endpoint, not in show/update/destroy. Any authenticated user of one company can read, edit, or delete another company's notes by ID. This is a distinct finding from the previously reported CustomerPolicy company-ownership omission (a different policy class and controller). Added CVSS V3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L Added CWE CWE-639 Added Reference https://github.com/crater-invoice/crater