vulnerability / NVI-00001985 / Revision 1
SolidInvoice: IDOR in LiveComponent allows same-company cross-user access to API tokens and notification transport settings
OSV carries this publisher advisory for solidinvoice/solidinvoice. This is an aggregated source copy; consult the original publisher and compare update dates.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
solidinvoice/solidinvoice
source listedECOSYSTEM: introduced 0; fixed 2.3.16
## Summary Four authorization bypass vulnerabilities in Symfony LiveComponent actions allow any authenticated user within a company to access, modify, or delete other users' API tokens and notification transport settings. The root cause is that LiveComponent actions accept entity IDs without verifying ownership, while the listing methods correctly filter by user. ## Findings ### 1. Cross-User API Token Revocation (MEDIUM) **File:** `src/UserBundle/Twig/Components/ApiTokens.php`, lines 50-55 The `revoke()` LiveAction accepts any `ApiToken` via `#[LiveArg]` without checking ownership. The `apiTokens()` method correctly filters by user (`getApiTokensForUser($this->security->getUser())`). ```php #[LiveAction] public function revoke(#[LiveArg] ApiToken $token): void { $this->apiTokenRepository->revoke($token); // No ownership check } ``` ### 2. Cross-User API Token History Disclosure (MEDIUM) **File:** `src/UserBundle/Twig/Components/ApiTokenHistory.php`, lines 30-55 The writable `$token` LiveProp performs `$this->apiTokenRepository->find($this->token)` without user verification. Exposes IP addresses, request methods, paths, and user agents from other users' API token usage
03 / Response
What to do next
- vendor patch
The original advisory lists fixed boundaries 2.3.16 for solidinvoice/solidinvoice. Confirm the publisher’s latest guidance.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-7vfx-4246-jcfh ↗
GitHub Advisory Database via OSV · vendor advisory
Observed . GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.