Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

High severity, with a CVSS score of 8.9, published 26 June 2026.

Which products and versions are affected?

solidinvoice/solidinvoice (Packagist) <= 2.3.15; SolidInvoice <= 2.3.15.

Is there a fix for This vulnerability?

A patch was published on 2026-06-26: Fixed in version 2.3.16 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is This vulnerability attacked?

It is attacked over the network, in a network appliance.

Check whether you run solidinvoice/solidinvoice (Packagist) or SolidInvoice at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

SolidInvoice IDOR in LiveComponent allows cross-user data access

Q: Is there a fix for This vulnerability?

A patch was published on 2026-06-26: Fixed in version 2.3.16 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is This vulnerability attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected?

Check whether you run solidinvoice/solidinvoice (Packagist) or SolidInvoice at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Severity: high · CVSS 8.9 · Published 2026-06-26

SolidInvoice, an open-source invoicing and billing application, contains multiple security flaws that allow users within the same company to access or modify each other's private data. An authenticated user could view or delete other users' API tokens and steal notification credentials for services like Slack, Discord, or Telegram. This could lead to unauthorized access to external communication channels and the exposure of sensitive integration keys.

Technologies: SolidInvoice. Vendors: Packagist, SolidInvoice.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: High severity, with a CVSS score of 8.9, published 26 June 2026.
Which products and versions are affected?: solidinvoice/solidinvoice (Packagist) <= 2.3.15; SolidInvoice <= 2.3.15.
Is there a fix for This vulnerability?: A patch was published on 2026-06-26: Fixed in version 2.3.16 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked over the network, in a network appliance.
Am I affected?: Check whether you run solidinvoice/solidinvoice (Packagist) or SolidInvoice at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

SolidInvoice is vulnerable to multiple Insecure Direct Object Reference (IDOR) flaws within its Symfony LiveComponent implementation. The root cause is that several LiveAction and LiveProp components (specifically ApiTokens, ApiTokenHistory, NotificationIntegrations, and NotificationTransportConfiguration) resolve entity IDs provided by the client without verifying if the requesting user owns the entity. While the application uses a CompanyFilter for tenant isolation, it lacks granular user-level authorization checks. Attackers can revoke API tokens, view token usage history (IPs and user agents), disclose notification transport credentials (API keys for Slack/Discord), or take over transport settings by overwriting the owner field. The issue is resolved in version 2.3.16.

Affected products

SolidInvoice SolidInvoice <= 2.3.15

Timeline

2026-05-25: disclosed
2026-06-26: advisory
2026-06-26: patched: Fixed in version 2.3.16

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.