Is this vulnerability remotely exploitable?

Yes. The affected oauth2.php endpoint is unauthenticated, and an attacker with network access to the application can send crafted requests to trigger deserialization, provided they can reference or influence the targeted serialized access_token data.

Does an attacker need valid credentials to exploit this?

No user authentication is required for the vulnerable endpoint itself. However, practical exploitation may depend on whether an attacker can create or modify OAuth2 records or otherwise cause controlled serialized data to be present in the `zz_oauth2` table.

What is the safest general fix pattern?

The safest pattern is to remove reliance on PHP's `unserialize()` for user-influenced or indirectly controlled data and replace it with safer, data-only formats like JSON. Where deserialization is truly necessary, enforce strict class whitelisting and ensure that only benign, data-only structures are ever deserialized.

Severity:

HIGH RISK

(7.2)

PHP Unsafe Deserialization (CWE-502) in OpenSTAManager OAuth2 Endpoint

CVE-2026-29782

Published:

Apr 2, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-94

HIGH RISK

HIGH

(8.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

Remote Code Execution by authenticated users via malicious file upload

May 10, 2026

CWE-94

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

Remote Code Execution by Authenticated Users

May 10, 2026

Vulnerability Type

Category:

Unsafe Deserialization

CWE:

CWE-502

Impact:

Remote Code Execution and Application Compromise

Severity:

HIGH RISK

(7.2)

CVSS Version:

3.1

Vulnerability Type

Category:

Unsafe Deserialization

CWE:

CWE-502

Impact:

Remote Code Execution and Application Compromise

Severity:

HIGH RISK

(7.2)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

PHP Unsafe Deserialization (CWE-502) in OpenSTAManager OAuth2 Endpoint

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal