# CVE-2026-61686: SolidInvoice: PHP unserialize() called on client-controlled data in DataGrid LiveComponent context prop

> An authenticated attacker can execute arbitrary code by sending a malicious serialized payload to the DataGrid component in SolidInvoice.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-4gj8-frx2-gmp6

## What is CVE-2026-61686?

CVE-2026-61686 is a high-severity unsafe deserialization vulnerability in SolidInvoice, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SolidInvoice is an open-source invoicing platform. Prior to version 3.0.1, the `DataGrid` LiveComponent deserializes a `context` prop value using PHP's `unserialize()` after receiving it from the client. Because the prop is marked `writable: true`, an authenticated attacker can supply an arbitrary PHP serialized payload. Version 3.0.1 fixes the issue.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-61686 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61686 is a high-severity unsafe deserialization vulnerability in SolidInvoice, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61686 exists.

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

## Sources

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

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