# CVE-2025-69213: OpenSTAManager has a SQL Injection in ajax_complete.php (get_sedi endpoint)

> An authenticated attacker can inject SQL code via the idanagrafica parameter in OpenSTAManager to gain unauthorized database access.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA: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:** 4 Feb 2026
- **Updated:** 4 Feb 2026
- **Also known as:** GHSA-w995-ff8h-rppg

## What is CVE-2025-69213?

CVE-2025-69213 is a high-severity SQL injection vulnerability in devcode-it openstamanager, published on 4 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenSTAManager is an open source management software for technical assistance and invoicing. In version 2.9.8 and prior, a SQL Injection vulnerability exists in the ajax_complete.php endpoint when handling the get_sedi operation. An authenticated attacker can inject malicious SQL code through the idanagrafica parameter, leading to unauthorized database access. At time of publication, no known patch exists.

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

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

2 open source packages ship an affected version, including devcode-it/openstamanager. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `devcode-it/openstamanager` | Packagist | All versions to 2.9.8 | None |
| `devcode-it/openstamanager` | Packagist | All versions to 2.9.8 | None |

Products: Devcode Openstamanager.

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

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

## Is CVE-2025-69213 being exploited?

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

Public exploit code:

- CVE-2025-69213 - OpenSTAManager has a SQL Injection in ajax_complete.php (get_sedi endpoint) (github_poc): https://github.com/lukasz-rybak/CVE-2025-69213

## Other vulnerabilities in devcode-it openstamanager

- [CVE-2026-27012](https://insights.sbomify.com/CVE-2026-27012/): Unauthenticated privilege escalation in OpenSTAManager via modules/utenti/actions.php (critical 9.8)
- [CVE-2025-69212](https://insights.sbomify.com/CVE-2025-69212/): OpenSTAManager has an OS Command Injection in P7M File Processing (critical 9.4)
- [CVE-2026-35470](https://insights.sbomify.com/CVE-2026-35470/): OpenSTAManager has a SQL Injection via righe Parameter in confronta_righe Modals (high 8.8)
- [CVE-2026-28805](https://insights.sbomify.com/CVE-2026-28805/): OpenSTAManager: Time-Based Blind SQL Injection via `options[stato]` Parameter (high 8.8)
- [CVE-2026-35168](https://insights.sbomify.com/CVE-2026-35168/): OpenSTAManager: SQL Injection via Aggiornamenti Module (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69213 is a high-severity SQL injection vulnerability in devcode-it openstamanager, published on 4 Feb 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-2025-69213 exists.

Affected packages and fixed versions:
- devcode-it/openstamanager (Packagist): affected all versions up to 2.9.8; no fix listed
- devcode-it/openstamanager (Packagist): affected all versions up to 2.9.8; no fix listed

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

## Sources

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

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