Improper Verification of Communication Channel in @theia/plugin-extGHSA-w6v7-w58j-pg5r
MEDIUMFix: eclipse-theia/theia#10125GHSA-w6v7-w58j-pg5r is a medium-severity (CVSS 6.1) CWE-940 vulnerability in @theia/plugin-ext. 1 public exploit reference exists, so weaponization risk is real. A fix is available for @theia/plugin-ext — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-w6v7-w58j-pg5r by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
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.
@theia/plugin-extnpmDescription
In versions of the @theia/plugin-ext component of Eclipse Theia prior to 1.18.0, Webview contents can be hijacked via postMessage().
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @theia/plugin-ext | all versions | 1.18.0npm install @theia/plugin-ext@1.18.0 |
Affected Products
theiaeclipseResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @theia/plugin-ext, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @theia/plugin-ext to 1.18.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w6v7-w58j-pg5r 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.
Frequently Asked Questions
Is GHSA-w6v7-w58j-pg5r in your dependencies?
Find it across npm, including transitive dependencies.