Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-whv5-4q2f-q68g | OpenSTAManager Affected by Remote Code Execution via Insecure Deserialization in OAuth2 |
Tue, 07 Apr 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:devcode:openstamanager:*:*:*:*:*:*:*:* |
Fri, 03 Apr 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 02 Apr 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Devcode
Devcode openstamanager |
|
| Vendors & Products |
Devcode
Devcode openstamanager |
Thu, 02 Apr 2026 14:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | OpenSTAManager: Remote Code Execution via Insecure Deserialization in OAuth2 | |
| Weaknesses | CWE-502 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-04-03T19:52:52.158Z
Reserved: 2026-03-04T16:26:02.898Z
Link: CVE-2026-29782
Updated: 2026-04-03T19:52:47.217Z
Status : Analyzed
Published: 2026-04-02T14:16:27.237
Modified: 2026-04-07T21:19:46.627
Link: CVE-2026-29782
No data.
OpenCVE Enrichment
Updated: 2026-04-08T19:56:31Z
Github GHSA