crater-invoice Crater 6.0.6 CustomerPolicy deleteCustomers privileges management

Summaryinfo

A vulnerability was found in crater-invoice Crater 6.0.6. It has been rated as critical. This affects the function Customer::deleteCustomers of the component CustomerPolicy. This manipulation causes privileges management. This vulnerability appears as CVE-2026-55739. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability has been found in crater-invoice Crater 6.0.6 and classified as critical. Affected by this vulnerability is the function Customer::deleteCustomers of the component CustomerPolicy. The manipulation with an unknown input leads to a privileges management vulnerability. The CWE definition for the vulnerability is CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Crater isolates data per company_id, and its Invoice/Estimate/Payment/Expense policies enforce both a Bouncer ability check and $user->hasCompany($model->company_id). CustomerPolicy's view/update/delete methods omit the company-ownership check entirely, checking only the blanket ability. Route-model-bound customer lookups and the bulk Customer::deleteCustomers() method are similarly unscoped (self::find($id) with no company filter). Any authenticated user of one company can read, reassign (steal), or delete another company's customer records, with deletion cascading to that customer's invoices and payments.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-55739 since 06/17/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/05/2026). MITRE ATT&CK project uses the attack technique T1068 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Rust Package

Vendor

• crater-invoice

Name

• Crater

Version

• 6.0.6

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion