Summary
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:
- Applications using the Auth0 Wordpress plugin with version between 5.0.0-BETA0 and 5.3.0,
- Auth0 Wordpress plugin uses the Auth0-PHP SDK with versions between 3.3.0 and 8.16.0.
Acknowledgement
Okta would like to thank Mohamed Amine Saidani (pwni) for discovering this vulnerability.
Impact
The application accepts file uploads without adequately restricting the file type or content. Typical impact: remote code execution if the uploaded file can be served and executed on the server.
GHSA-W22C-PW5M-482X has a CVSS score of 3.3 (Low). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.4.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Upgrade Auth0 Wordpress plugin to version 5.4.0 or greater.
Frequently Asked Questions
- What is GHSA-W22C-PW5M-482X? GHSA-W22C-PW5M-482X is a low-severity unrestricted upload of dangerous file types vulnerability in auth0/wordpress (composer), affecting versions > 5.0.0-BETA0, <= 5.3.0. It is fixed in 5.4.0. The application accepts file uploads without adequately restricting the file type or content.
- How severe is GHSA-W22C-PW5M-482X? GHSA-W22C-PW5M-482X has a CVSS score of 3.3 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of auth0/wordpress are affected by GHSA-W22C-PW5M-482X? auth0/wordpress (composer) versions > 5.0.0-BETA0, <= 5.3.0 is affected.
- Is there a fix for GHSA-W22C-PW5M-482X? Yes. GHSA-W22C-PW5M-482X is fixed in 5.4.0. Upgrade to this version or later.
- Is GHSA-W22C-PW5M-482X exploitable, and should I be worried? Whether GHSA-W22C-PW5M-482X is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-W22C-PW5M-482X is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-W22C-PW5M-482X? Upgrade
auth0/wordpressto 5.4.0 or later.