Loading vulnerability…
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.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This five-file standalone Python repository contains an operational exploit in exploit.py, documentation in README.md, a requests dependency, and standard license/git-ignore files. It targets OpenSTAManager 2.9.x (tested on 2.9.8) by logging in as an administrator and abusing the Aggiornamenti module's unrestricted SQL runner to insert a phpggc-generated Monolog 3 FW1 serialized object into zz_oauth2.access_token. A request to oauth2.php with the selected state causes unrestricted PHP unserialize() and triggers the gadget's file-write behavior. The written PHP webshell then provides arbitrary command execution as the web-server account, with command, interactive, drop-only, and Bash reverse-shell modes. The script also appends DDL statements to force a database commit, can use a supplied prebuilt payload, checks a files/ webshell fallback, and removes the injected OAuth2 row unless --keep is specified.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.