CVE-2025-47275 CRITICAL

CVE-2025-47275: Brute Force Authentication Tags of CookieStore Sessions in Auth0-PHP SDK

Vendor Auth0
Product auth0-PHP
Weakness CWE-287 · Improper authentication
Published May 15, 2025
Last update May 22, 2025

CVSS base score

9.1/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality High
Integrity High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

What the vulnerability does

01Description

Auth0-PHP provides the PHP SDK for Auth0 Authentication and Management APIs. Starting in version 8.0.0-BETA1 and prior to version 8.14.0, session cookies of applications using the Auth0-PHP SDK configured with CookieStore have authentication tags that can be brute forced, which may result in unauthorized access. Certain pre-conditions are required to be vulnerable to this issue: Applications using the Auth0-PHP SDK, or the Auth0/symfony, Auth0/laravel-auth0, and Auth0/wordpress SDKs that rely on the Auth0-PHP SDK; and session storage configured with CookieStore. Upgrade Auth0/Auth0-PHP to v8.14.0 to receive a patch. As an additional precautionary measure, rotating cookie encryption keys is recommended. Note that once updated, any previous session cookies will be rejected.

Explanation of Vulnerability in Simple Terms

02Summary

Auth0's PHP SDK versions 8.0.0-BETA1 through 8.13.x contain an authentication bypass flaw. An attacker can bypass authentication checks without valid credentials, gaining unauthorized access to protected resources. The vulnerability affects the SDK's core authentication logic and requires no user interaction or special privileges to exploit.

What an attacker can do

03Attacker Capabilities

Bypass authentication and gain unauthorized access to protected resources without valid credentials.

Potential impact on your site

04Site Impact

Attackers can access your site and its data without logging in, compromising user accounts and sensitive information.

Conditions required to exploit

05Prerequisites

Network access to the application; no authentication or user interaction required.

Key dates

06Disclosure timeline

May 15, 2025 CVE published
May 22, 2025 Record updated