# CVE-2026-24418: OpenSTAManager has an SQL Injection vulnerability in the Scadenzario bulk operations module

> Attackers can extract sensitive data via SQL injection in the Scadenzario module due to lack of input validation.

- **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:** 6 Feb 2026
- **Updated:** 6 Feb 2026
- **Also known as:** GHSA-4xwv-49c8-fvhq

## What is CVE-2026-24418?

CVE-2026-24418 is a high-severity SQL injection vulnerability in devcode-it openstamanager, published on 6 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. OpenSTAManager v2.9.8 and earlier contain a critical Error-Based SQL Injection vulnerability in the bulk operations handler for the Scadenzario (Payment Schedule) module. The application fails to validate that elements of the id_records array are integers before using them in an SQL IN() clause, allowing attackers to inject arbitrary SQL commands and extract sensitive data through XPATH error messages.

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

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

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-2026-24418?

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

## Is CVE-2026-24418 being exploited?

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

Public exploit code:

- OpenSTAManager v2.9.8 and earlier contain a critical Error-Based SQL Injection vulnerability in the bulk operations handler for the Scadenzario (Payment Schedule) module.  (github_poc): https://github.com/BridgerAlderson/CVE-2026-24418
- CVE-2026-24418 - OpenSTAManager has a SQL Injection vulnerability in the Scadenzario bulk operations module (github_poc): https://github.com/lukasz-rybak/CVE-2026-24418

## 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-2026-24418 and fix it if it is affected.

What it is: CVE-2026-24418 is a high-severity SQL injection vulnerability in devcode-it openstamanager, published on 6 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-2026-24418 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-2026-24418/ (Markdown: https://insights.sbomify.com/CVE-2026-24418/index.md)
```

## Sources

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

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