GHSA-pwhf-39xg-4rxw
MEDIUMGHSA-pwhf-39xg-4rxw is a medium-severity (CVSS 6.8) CWE-77 vulnerability in @backstage/techdocs-common. O3 Security confirms whether GHSA-pwhf-39xg-4rxw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Script injection
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
@backstage/techdocs-commonnpmDescription
Impact
A malicious internal actor is able to upload documentation content with malicious scripts. These scripts would normally be sanitized by the TechDocs frontend, but by tricking a user to visit the content via the TechDocs API, the content sanitazion will be bypassed. If the TechDocs API is hosted on the same origin as the Backstage app or other backend plugins, this may give access to sensitive data.
The ability to upload malicious content may be limited by internal code review processes, unless the chosen TechDocs deployment method is to use an object store and the actor has access to upload files directly to that store.
Patches
The vulnerability is patched in the 0.6.4 release of @backstage/techdocs-common.
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/techdocs-common | all versions | 0.6.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @backstage/techdocs-common. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @backstage/techdocs-common to 0.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pwhf-39xg-4rxw is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-pwhf-39xg-4rxw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-pwhf-39xg-4rxw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-pwhf-39xg-4rxw in your dependencies?
O3 detects GHSA-pwhf-39xg-4rxw across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.