GHSA-wg6p-jmpc-xjmr
HIGHGHSA-wg6p-jmpc-xjmr is a high-severity (CVSS 8) Code Injection vulnerability in @backstage/plugin-scaffolder-backend. O3 Security confirms whether GHSA-wg6p-jmpc-xjmr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Backstage Scaffolder plugin has insecure sandbox
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
@backstage/plugin-scaffolder-backendnpmDescription
The Backstage scaffolder-backend plugin uses a templating library that requires a sandbox, as it by design allows for code injection. The library used for this sandbox so far has been vm2, but in light of several past vulnerabilities and existing vulnerabilities that may not have a fix, the plugin has switched to using a different sandbox library.
Impact
A malicious actor with write access to a registered scaffolder template could manipulate the template in a way that allows for remote code execution on the scaffolder-backend instance. This was only exploitable in the template YAML definition itself and not by user input data.
Patches
This is vulnerability is fixed in version 1.15.0 of @backstage/plugin-scaffolder-backend.
Workarounds
Note that the Backstage Threat Model states that scaffolder templates are considered to be a sensitive area that with the recommendation that you control access and perform manual reviews of changes to the scaffolder templates. The exploit is of a nature where it is easily discoverable in manual review.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @backstage/plugin-scaffolder-backend | all versions | 1.15.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @backstage/plugin-scaffolder-backend. 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/plugin-scaffolder-backend to 1.15.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wg6p-jmpc-xjmr 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-wg6p-jmpc-xjmr 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-wg6p-jmpc-xjmr. 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-wg6p-jmpc-xjmr in your dependencies?
O3 detects GHSA-wg6p-jmpc-xjmr across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.