CVE-2025-48951 Auth0-PHP SDK Deserialization of Untrusted Data vulnerability
Attackers can execute arbitrary code by sending malicious serialized data in cookies to applications using the Auth0-PHP SDK.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-48951?
CVE-2025-48951 is a critical unsafe deserialization vulnerability in auth0-PHP, published on 3 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Auth0-PHP is a PHP SDK for Auth0 Authentication and Management APIs. Versions 8.0.0-BETA3 prior to 8.3.1 contain a vulnerability due to insecure deserialization of cookie data. If exploited, since SDKs process cookie content without prior authentication, a threat actor could send a specially crafted cookie containing malicious serialized data. Applications using the Auth0-PHP SDK are affected, as are applications using the Auth0/symfony, Auth0/laravel-auth0, or Auth0/wordpress SDKs, because those SDKsrely on the Auth0-PHP SDK versions from 8.0.0-BETA3 until 8.14.0. Version 8.3.1 contains a patch for the issue.
Weakness: CWE-502
Which versions are affected by CVE-2025-48951?
2 open source packages ship an affected version, including auth0/auth0-php.
| Package | Affected | Fixed in |
|---|---|---|
auth0/auth0-php Packagist | From 8.0.0-BETA3 | 8.3.1 |
auth0/auth0-php Packagist | From 8.0.0-BETA3 | 8.3.1 |
How do I fix CVE-2025-48951?
Upgrade auth0/auth0-php to 8.3.1 or later.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2025-48951 being exploited?
There is no known exploitation of CVE-2025-48951 in the wild and no public exploit code.
Sources
Also known as GHSA-v9m8-9xxp-q492.