SolidInvoice: IDOR in LiveComponent allows same-company cross-user access to API tokens and notification transport settings
Date: 2026-06
Affected: composer/solidinvoice/solidinvoice
Attack vector: auth-bypass
Category: vulnerability-disclosure
Severity: High
CWE: CWE-639
CWE-862

## 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. ### 3. Cross-User Notification Transport Settings Disclosure (HIGH) **File:** `src/NotificationBundle/Twig/Components/NotificationIntegrations.php`, lines 48-55 The `integration()` method performs `$this->repository->find($this->setting)` using a writable LiveProp without user check. The `enabl


Mitigations:

Architectural layers (MAESTRO):