# CVE-2026-29925: Server-side request forgery in n/a

> Attackers can exploit SSRF in Invoice Ninja to access internal resources or bypass security controls.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **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:** 30 Mar 2026
- **Updated:** 30 Mar 2026
- **Also known as:** GHSA-r7m8-874r-4g5v

## What is CVE-2026-29925?

CVE-2026-29925 is a high-severity server-side request forgery vulnerability in n/a, published on 30 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Invoice Ninja v5.12.46 and v5.12.48 is vulnerable to Server-Side Request Forgery (SSRF) in CheckDatabaseRequest.php.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Invoiceninja Invoice Ninja.

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

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

## Is CVE-2026-29925 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-33898](https://insights.sbomify.com/CVE-2021-33898/): Deserialization in n/a (high 8.1)
- [CVE-2021-3977](https://insights.sbomify.com/CVE-2021-3977/): Cross-site Scripting (XSS) - Stored in invoiceninja/invoiceninja (medium 6.5)
- [CVE-2026-33628](https://insights.sbomify.com/CVE-2026-33628/): Invoice Ninja Denylist Bypass may Lead to Stored XSS via Invoice Line Items (medium 5.4)
- [CVE-2026-33742](https://insights.sbomify.com/CVE-2026-33742/): Invoice Ninja has Stored XSS via Markdown HTML Injection in Product Notes (medium 5.4)
- [CVE-2017-1000466](https://insights.sbomify.com/CVE-2017-1000466/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-29925 is a high-severity server-side request forgery vulnerability in n/a, published on 30 Mar 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-29925 exists.

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

## Sources

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

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