What is CVE-2023-6813?

CVE-2023-6813 is a medium-severity cross-site scripting (XSS) vulnerability in auth0/wordpress (composer), affecting versions <= 4.6.0. It is fixed in 4.6.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2023-6813?

CVE-2023-6813 has a CVSS score of 6.1 (Medium). 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 CVE-2023-6813?

auth0/wordpress (composer) versions <= 4.6.0 is affected.

Is there a fix for CVE-2023-6813?

Yes. CVE-2023-6813 is fixed in 4.6.1. Upgrade to this version or later.

Is CVE-2023-6813 exploitable, and should I be worried?

Whether CVE-2023-6813 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.

What actually determines whether CVE-2023-6813 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 CVE-2023-6813?

Upgrade auth0/wordpress to 4.6.1 or later.

CVE-2023-6813 in auth0/wordpress | Intelligent Application Security

Q: How severe is CVE-2023-6813?

CVE-2023-6813 has a CVSS score of 6.1 (Medium). 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.

Q: Which versions of auth0/wordpress are affected by CVE-2023-6813?

auth0/wordpress (composer) versions <= 4.6.0 is affected.

Q: Is there a fix for CVE-2023-6813?

Yes. CVE-2023-6813 is fixed in 4.6.1. Upgrade to this version or later.

Q: Is CVE-2023-6813 exploitable, and should I be worried?

Whether CVE-2023-6813 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.

Q: What actually determines whether CVE-2023-6813 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.

Q: How do I fix CVE-2023-6813?

Upgrade auth0/wordpress to 4.6.1 or later.

Summary

Impact

The Auth0 WordPress plugin allows site administrators to opt-in to allowing the use of a wle parameter, which can be passed to the WordPress login page by end users. When this parameter is supplied using an expected value (which is randomly generated by the plugin, by default), the end user can fallback to using WordPress' native authentication behavior. (This is generally intended as an emergency fallback for administrators to still be able to access their dashboard in the event something goes wrong.)

In previous versions of the plugin, under specific conditions, this parameter could potentially accept an arbitrary string that would be improperly rendered, potentially allowing for a cross-site scripting (XSS) attack on the login page.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2023-6813 has a CVSS score of 6.1 (Medium). The vector is network-reachable, no privileges required, and user interaction required. 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 (4.6.1); upgrading removes the vulnerable code path.

Affected versions

auth0/wordpress (<= 4.6.0)

Security releases

auth0/wordpress → 4.6.1 (composer)

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.

See it in your environment

Remediation advice

Please upgrade to v4.6.1 of the plugin to resolve the issue.

Frequently Asked Questions

What is CVE-2023-6813? CVE-2023-6813 is a medium-severity cross-site scripting (XSS) vulnerability in auth0/wordpress (composer), affecting versions <= 4.6.0. It is fixed in 4.6.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2023-6813? CVE-2023-6813 has a CVSS score of 6.1 (Medium). 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 CVE-2023-6813? auth0/wordpress (composer) versions <= 4.6.0 is affected.
Is there a fix for CVE-2023-6813? Yes. CVE-2023-6813 is fixed in 4.6.1. Upgrade to this version or later.
Is CVE-2023-6813 exploitable, and should I be worried? Whether CVE-2023-6813 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 CVE-2023-6813 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 CVE-2023-6813? Upgrade auth0/wordpress to 4.6.1 or later.

Other vulnerabilities in auth0/wordpress

CVE-2023-6813