Quick answers
- Is CVE-2026-35470 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-35470 being exploited in the wild.
- How severe is CVE-2026-35470?
- High severity, with a CVSS score of 8.8, published 6 April 2026.
- Which products and versions are affected?
- devcode-it/openstamanager (Packagist) ECOSYSTEM:introduced=0,fixed=2.10.2.
- Is there a fix for CVE-2026-35470?
- Yes. devcode-it/openstamanager (Packagist): upgrade to 2.10.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-35470 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-35470?
- Check whether you run Devcode Openstamanager or devcode-it/openstamanager (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- devcode-it/openstamanager (Packagist): upgrade to 2.10.2 or later
composer require devcode-it/openstamanager:^2.10.2
Technical details
An SQL injection vulnerability exists in OpenSTAManager versions prior to 2.10.2 due to improper sanitization of the 'righe' GET parameter in 'confronta_righe.php' files across multiple modules (including invoices, interventions, and contracts). The application directly concatenates the 'righe' parameter into SQL IN() clauses without using parameterized queries or input validation. An authenticated attacker with low privileges can exploit this via network requests to execute arbitrary SQL commands. This allows for the extraction of sensitive data via error-based techniques (e.g., EXTRACTVALUE) or potential data modification through stacked queries. The issue is resolved in version 2.10.2 by implementing the prepare() function for SQL escaping.
Affected products
- devcode-it OpenSTAManager < 2.10.2
Identifiers
- CVE-2026-35470
- GHSA-mmm5-3g4x-qw39
Timeline
- 2026-04-01: advisory: GitHub Security Advisory published
- 2026-04-06: disclosed: NVD publication date
- 2026-03-17: patched: Version 2.10.2 released