# CVE-2026-27012: Unauthenticated privilege escalation in OpenSTAManager via modules/utenti/actions.php

> Unauthenticated attackers can escalate privileges by modifying user groups via a vulnerable action script in OpenSTAManager.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Mar 2026
- **Updated:** 4 Mar 2026
- **Also known as:** GHSA-247v-7cw6-q57v

## What is CVE-2026-27012?

CVE-2026-27012 is a critical vulnerability in devcode-it openstamanager, published on 3 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenSTAManager is an open source management software for technical assistance and invoicing. In 2.9.8 and earlier, a privilege escalation and authentication bypass vulnerability in OpenSTAManager allows any attacker to arbitrarily change a user's group (idgruppo) by directly calling modules/utenti/actions.php. This can promote an existing account (e.g. agent) into the Amministratori group as well as demote any user including existing administrators.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

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-27012?

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

## Is CVE-2026-27012 being exploited?

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

## Other vulnerabilities in devcode-it openstamanager

- [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)
- [CVE-2025-69214](https://insights.sbomify.com/CVE-2025-69214/): OpenSTAManager has a SQL Injection in ajax_select.php (componenti endpoint) (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-27012 is a critical vulnerability in devcode-it openstamanager, published on 3 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27012 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-27012/ (Markdown: https://insights.sbomify.com/CVE-2026-27012/index.md)
```

## Sources

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

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