CVE-2021-43776 — @backstage/plugin-auth-ba…
HIGHCVE-2021-43776 is a high-severity (CVSS 7.4) Cross-site Scripting (XSS) vulnerability in @backstage/plugin-auth-backend. A fix is available for @backstage/plugin-auth-backend — see the affected versions and patch details below.
Cross-Site Scripting vulnerability in @backstage/plugin-auth-backend
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@backstage/plugin-auth-backendnpmDescription
Impact
This vulnerability allows a malicious actor to trick another user into visiting a vulnerable URL that executes an XSS attack. This attack can potentially allow the attacker to exfiltrate access tokens or other secrets from the user's browser. The default CSP does prevent this attack, but it is expected that some deployments have these policies disabled due to incompatibilities.
Patches
This is vulnerability is patched in version 0.4.9 of @backstage/plugin-auth-backend.
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 Backstage README
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @backstage/plugin-auth-backend | all versions | 0.4.9npm install @backstage/plugin-auth-backend@0.4.9 |
Affected Products
auth backendlinuxfoundationDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @backstage/plugin-auth-backend, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @backstage/plugin-auth-backend to 0.4.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-43776 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2021-43776 in your dependencies?
Find it across npm, including transitive dependencies.