# CVE-2026-61608: Missing authorization in SolidInvoice

> Attackers can use leaked or old invitation links to gain unauthorized access to companies because invitation tokens lack expiration dates.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-5gcp-fm29-jgrp

## What is CVE-2026-61608?

CVE-2026-61608 is a medium-severity missing authorization vulnerability in SolidInvoice, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

SolidInvoice is an open-source invoicing platform. Prior to version 3.0.1, `UserInvitation` entities have no expiry timestamp. Invitation links mailed to users remain valid indefinitely, meaning a leaked, forwarded, or archived invitation email can be used at any time in the future to join a company or silently add a compromised email account to a company. Version 3.0.1 fixes the issue.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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


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

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

## Is CVE-2026-61608 being exploited?

There is no known exploitation of CVE-2026-61608 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61608 is a medium-severity missing authorization vulnerability in SolidInvoice, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-61608 in the wild and no public exploit code.

Affected product: SolidInvoice. 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-61608/ (Markdown: https://insights.sbomify.com/CVE-2026-61608/index.md)
```

## Sources

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

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