# CVE-2026-55383: InvoiceShelf: Public EmailLog token type confusion allows cross-company invoice disclosure

> Attackers can access other companies' invoices and estimates by exploiting token type confusion and expired token handling in public routes.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-73q7-2953-8gvx

## What is CVE-2026-55383?

CVE-2026-55383 is a high-severity missing authorization vulnerability in InvoiceShelf, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

InvoiceShelf is an open-source web & mobile app that helps track expenses, payments and create professional invoices and estimates. Prior to version 2.4.0, InvoiceShelf public customer invoice, estimate, and payment routes use an EmailLog token's numeric mailable_id without verifying mailable_type, and the JSON handlers do not enforce EmailLog::isExpired. A token issued for one document type can therefore disclose a different company's document when numeric identifiers collide, and an expired token can remain usable on the JSON routes GET /customer/invoices/{email_log:token}, GET /customer/estimates/{email_log:token}, and GET /customer/payments/{email_log:token}. View handlers can also mark a mismatched invoice or estimate as viewed and send a notification. This issue is fixed in version 2.4.0.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-55383?


## How do I fix CVE-2026-55383?

No fix has been published for CVE-2026-55383 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-55383 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55383 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55383 and fix it if it is affected.

What it is: CVE-2026-55383 is a high-severity missing authorization vulnerability in InvoiceShelf, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55383 exists.

Affected product: InvoiceShelf. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55383/ (Markdown: https://insights.sbomify.com/CVE-2026-55383/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55383
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55383
- OSV: https://osv.dev/vulnerability/CVE-2026-55383

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55383/
Summaries are generated and may contain mistakes; the official description above is the record.