CVE-2026-29782: devcode-it openstamanager · Deserialization of Untrusted Data
Affects devcode-it openstamanagerSource CVE Database V5
Not known to be exploited · CVSS 7.2 High : upgrade to 2.10.2 soon.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.10.2
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade openstamanager and devcode-it/openstamanager to 2.10.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| devcode-itopenstamanager | Affected
| Fixed in
|
GitHubdevcode-it/openstamanagerpkg:github/devcode-it/openstamanagerOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch fixing this vulnerability is available in OpenSTAManager version 2.10.2. Users should upgrade to version 2.10.2 or later to remediate this issue. No other mitigation guidance is provided or required as the vulnerability is addressed by the official fix.
Description
OpenSTAManager is an open source management software for technical assistance and invoicing. Prior to version 2.10.2, the oauth2.php file in OpenSTAManager is an unauthenticated endpoint ($skip_permissions = true). It loads a record from the zz_oauth2 table using the attacker-controlled GET parameter state, and during the OAuth2 configuration flow calls unserialize() on the access_token field without any class restriction. This issue has been patched in version 2.10.2.