Skip to content

Brute Force Authentication Tags of CookieStore Sessions in Auth0-PHP SDK

Critical severity GitHub Reviewed Published May 15, 2025 in auth0/auth0-PHP • Updated May 22, 2025

Package

composer auth0/auth0-php (Composer)

Affected versions

>= 8.0.0-BETA1, < 8.14.0

Patched versions

8.14.0

Description

Overview
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.

Am I Affected?
You are affected by this vulnerability if you meet the following pre-conditions:

  1. Applications using the Auth0-PHP SDK, or the following SDKs that rely on the Auth0-PHP SDK:
    a. Auth0/symfony,
    b. Auth0/laravel-auth0,
    c. Auth0/wordpress,
  2. Session storage configured with CookieStore.

Fix
Upgrade Auth0/Auth0-PHP to v8.14.0. As an additional precautionary measure, we recommend rotating your cookie encryption keys. Note that once updated, any previous session cookies will be rejected.

Acknowledgement
Okta would like to thank Félix Charette for discovering this vulnerability.

References

@femi-nonemu femi-nonemu published to auth0/auth0-PHP May 15, 2025
Published by the National Vulnerability Database May 15, 2025
Published to the GitHub Advisory Database May 16, 2025
Reviewed May 16, 2025
Last updated May 22, 2025

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(11th percentile)

Weaknesses

CVE ID

CVE-2025-47275

GHSA ID

GHSA-g98g-r7gf-2r25

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.