# CVE-2025-67811: SQL injection in n/a

> Authenticated attackers can inject SQL commands via API endpoints to access or modify sensitive database data in Area9 Rhapsode.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 9 Jan 2026
- **Updated:** 9 Jan 2026
- **Also known as:** GHSA-r8x9-f3r5-3x8j

## What is CVE-2025-67811?

CVE-2025-67811 is a medium-severity SQL injection vulnerability in n/a, published on 9 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Area9 Rhapsode 1.47.3 allows SQL Injection via multiple API endpoints accessible to authenticated users. Insufficient input validation allows remote attackers to inject arbitrary SQL commands, resulting in unauthorized database access and potential compromise of sensitive data. Fixed in v.1.47.4 and beyond.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-67811?

It affects 1 product.


Products: Area9lyceum Rhapsode.

## How do I fix CVE-2025-67811?

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

## Is CVE-2025-67811 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-67810](https://insights.sbomify.com/CVE-2025-67810/): Path traversal in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-67811 and fix it if it is affected.

What it is: CVE-2025-67811 is a medium-severity SQL injection vulnerability in n/a, published on 9 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-67811 in the wild and no public exploit code.

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

## Sources

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

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