Skip to content

auth0-PHP SDK Does Not Properly Handle File Types in Bulk User Import

Low severity GitHub Reviewed Published Oct 1, 2025 in auth0/auth0-PHP • Updated Oct 1, 2025

Package

composer auth0/auth0-php (Composer)

Affected versions

>= 3.3.0, <= 8.16.0

Patched versions

8.17.0

Description

Overview

In applications built with the Auth0-PHP SDK, the Bulk User Import endpoint does not validate the file path wrapper or value. Without proper validation, affected applications may accept arbitrary file paths or URLs.

Am I affected?

You are affected by this vulnerability if you meet the following preconditions:

  1. Applications using the Auth0-PHP SDK, versions between v3.3.0 and v8.16.0, or
  2. Applications using the following SDKs that rely on the Auth0-PHP SDK versions between v3.3.0 and v8.16.0:
    a. Auth0/symfony,
    b. Auth0/laravel-auth0,
    c. Auth0/wordpress.

Fix

Upgrade Auth0/Auth0-PHP to version 8.17.0 or greater.

Acknowledgement

Okta would like to thank Mohamed Amine Saidani (pwni) for discovering this vulnerability.

References

@jennyyang-okta jennyyang-okta published to auth0/auth0-PHP Oct 1, 2025
Published by the National Vulnerability Database Oct 1, 2025
Published to the GitHub Advisory Database Oct 1, 2025
Reviewed Oct 1, 2025
Last updated Oct 1, 2025

Severity

Low

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
High
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
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:H/PR:H/UI:N/S:U/C:L/I:L/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.
(25th percentile)

Weaknesses

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Learn more on MITRE.

Unrestricted Upload of File with Dangerous Type

The product allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment. Learn more on MITRE.

CVE ID

CVE-2025-58769

GHSA ID

GHSA-9mh6-g99m-ppcw

Source code

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