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 ->hasCompany(->company_id). Any authenticated user of one company can read...
Vendor
crater-invoice vulnerabilities
10 published CVES affecting crater-invoice, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 10
- Critical
- 0
- High
- 6
- Medium
- 4
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Products
Latest crater-invoice CVEs
Newest publication first
-
HighCVSS 8.2 EPSS 0.37%
-
HighCVSS 8.2 EPSS 0.37%
Crater isolates data per company_id, and its Invoice/Estimate/Payment/Expense policies enforce both a Bouncer ability check and ->hasCompany(->company_id). CustomerPolicy's view/update/delete methods omit the company-ownership check entirely, checking only the blanket ability. Ro...
-
CVE-2022-1032 Insecure deserialization of not validated module file in crater-invoice/crater
PublishedHighCVSS 7.2 EPSS 1.6%Insecure deserialization of not validated module file in GitHub repository crater-invoice/crater prior to 6.0.6.
-
HighCVSS 7.8 EPSS 0.92%
Unrestricted Upload of File with Dangerous Type in GitHub repository crater-invoice/crater prior to 6.0.6.
-
MediumCVSS 4.3 EPSS 0.43%
Cross-Site Request Forgery (CSRF) in GitHub repository crater-invoice/crater prior to 6.0.4.
-
MediumCVSS 6.5 EPSS 0.96%
Business Logic Errors in GitHub repository crater-invoice/crater prior to 6.0.5.
-
MediumCVSS 5.4 EPSS 0.61%
Cross-site Scripting (XSS) - Stored in Packagist bytefury/crater prior to 6.0.2.
-
MediumCVSS 5.3 EPSS 1.3%
Improper Access Control in GitHub repository crater-invoice/crater prior to 6.0.2.
-
HighCVSS 7.2 EPSS 1.5%
Unrestricted Upload of File with Dangerous Type in GitHub repository crater-invoice/crater prior to 6.0.
-
HighCVSS 8.8 EPSS 1.5%
crater is vulnerable to Unrestricted Upload of File with Dangerous Type
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.