What is CVE-2023-25571?

CVE-2023-25571 is a medium-severity cross-site scripting (XSS) vulnerability in @backstage/core-components (npm), affecting versions < 0.12.4. It is fixed in 0.12.4, 1.2.0, 1.7.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-25571?

CVE-2023-25571 has a CVSS score of 6.8 (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 packages are affected by CVE-2023-25571?

@backstage/core-components (npm) versions < 0.12.4; @backstage/catalog-model (npm) versions < 1.2.0; @backstage/plugin-catalog-backend (npm) versions < 1.7.2.

Is there a fix for CVE-2023-25571?

Yes. CVE-2023-25571 is fixed in 0.12.4, 1.2.0, 1.7.2. Upgrade to this version or later.

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

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

Upgrade: @backstage/core-components to 0.12.4 or later, @backstage/catalog-model to 1.2.0 or later, @backstage/plugin-catalog-backend to 1.7.2 or later.

CVE-2023-25571 in @backstage/core-components

Q: How severe is CVE-2023-25571?

CVE-2023-25571 has a CVSS score of 6.8 (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 packages are affected by CVE-2023-25571?

@backstage/core-components (npm) versions < 0.12.4; @backstage/catalog-model (npm) versions < 1.2.0; @backstage/plugin-catalog-backend (npm) versions < 1.7.2.

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

Yes. CVE-2023-25571 is fixed in 0.12.4, 1.2.0, 1.7.2. Upgrade to this version or later.

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

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

Upgrade: @backstage/core-components to 0.12.4 or later, @backstage/catalog-model to 1.2.0 or later, @backstage/plugin-catalog-backend to 1.7.2 or later.

Summary

Cross site scripting Vulnerability in backstage Software Catalog

Workarounds

The general practice of limiting access to modifying catalog content and requiring code reviews greatly helps mitigate this vulnerability.

For more information

If you have any questions or comments about this advisory:

Open an issue in the Backstage repository
Visit our chat, linked to in the Backstage README

Impact

This vulnerability allows a malicious actor with access to add or modify content in an instance of the Backstage software catalog to inject script URLs in the entities stored in the catalog. If users of the catalog then click on said URLs, that can lead to an XSS attack.

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-25571 has a CVSS score of 6.8 (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 (0.12.4, 1.2.0, 1.7.2); upgrading removes the vulnerable code path.

Affected versions

@backstage/core-components (< 0.12.4) @backstage/catalog-model (< 1.2.0) @backstage/plugin-catalog-backend (< 1.7.2)

Security releases

@backstage/core-components → 0.12.4 (npm) @backstage/catalog-model → 1.2.0 (npm) @backstage/plugin-catalog-backend → 1.7.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

This vulnerability has been patched in both the frontend and backend implementations. The default Link component from @backstage/core-components will now reject javascript: URLs, and there is a global override of window.open to do the same.

In addition the catalog model as well as the catalog backend now has additional validation built in that prevents javascript: URLs in known annotations.

Frequently Asked Questions

What is CVE-2023-25571? CVE-2023-25571 is a medium-severity cross-site scripting (XSS) vulnerability in @backstage/core-components (npm), affecting versions < 0.12.4. It is fixed in 0.12.4, 1.2.0, 1.7.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-25571? CVE-2023-25571 has a CVSS score of 6.8 (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 packages are affected by CVE-2023-25571?
- @backstage/core-components (npm) (versions < 0.12.4)
- @backstage/catalog-model (npm) (versions < 1.2.0)
- @backstage/plugin-catalog-backend (npm) (versions < 1.7.2)
Is there a fix for CVE-2023-25571? Yes. CVE-2023-25571 is fixed in 0.12.4, 1.2.0, 1.7.2. Upgrade to this version or later.
Is CVE-2023-25571 exploitable, and should I be worried? Whether CVE-2023-25571 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-25571 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-25571?
- Upgrade @backstage/core-components to 0.12.4 or later
- Upgrade @backstage/catalog-model to 1.2.0 or later
- Upgrade @backstage/plugin-catalog-backend to 1.7.2 or later