What is CVE-2023-32325?

CVE-2023-32325 is a medium-severity cross-site scripting (XSS) vulnerability in posthog-js (npm), affecting versions < 1.57.2. It is fixed in 1.57.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2023-32325?

CVE-2023-32325 has a CVSS score of 5.4 (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 posthog-js are affected by CVE-2023-32325?

posthog-js (npm) versions < 1.57.2 is affected.

Is there a fix for CVE-2023-32325?

Yes. CVE-2023-32325 is fixed in 1.57.2. Upgrade to this version or later.

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

Whether CVE-2023-32325 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-32325 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-32325?

Upgrade posthog-js to 1.57.2 or later.

CVE-2023-32325 in posthog-js

Q: How severe is CVE-2023-32325?

CVE-2023-32325 has a CVSS score of 5.4 (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 posthog-js are affected by CVE-2023-32325?

posthog-js (npm) versions < 1.57.2 is affected.

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

Yes. CVE-2023-32325 is fixed in 1.57.2. Upgrade to this version or later.

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

Whether CVE-2023-32325 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-32325 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-32325?

Upgrade posthog-js to 1.57.2 or later.

Summary

Potential for cross-site scripting in PostHog-js

Workarounds

This isn't an issue for sites that have a Content Security Policy in place.
Using the HTML tracking snippet on PostHog Cloud always guarantees the latest version of the library, in that case no action is required to upgrade to the patched version.

References

We will publish details of the vulnerability in 30 days as per our security policy.

Impact

Potential for cross-site scripting in posthog-js.

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-32325 has a CVSS score of 5.4 (Medium). The vector is network-reachable, low 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 (1.57.2); upgrading removes the vulnerable code path.

Affected versions

posthog-js (< 1.57.2)

Security releases

posthog-js → 1.57.2 (npm)

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.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The problem has been patched in posthog-js version 1.57.2.

Frequently Asked Questions

What is CVE-2023-32325? CVE-2023-32325 is a medium-severity cross-site scripting (XSS) vulnerability in posthog-js (npm), affecting versions < 1.57.2. It is fixed in 1.57.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2023-32325? CVE-2023-32325 has a CVSS score of 5.4 (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 posthog-js are affected by CVE-2023-32325? posthog-js (npm) versions < 1.57.2 is affected.
Is there a fix for CVE-2023-32325? Yes. CVE-2023-32325 is fixed in 1.57.2. Upgrade to this version or later.
Is CVE-2023-32325 exploitable, and should I be worried? Whether CVE-2023-32325 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-32325 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-32325? Upgrade posthog-js to 1.57.2 or later.