GHSA-c6cw-g7fc-4gwc
MEDIUMLara-zeus Dynamic Dashboard and Artemis do not validate paragraph widget values which can be used for XSS
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
lara-zeus/dynamic-dashboard🐘lara-zeus/artemisReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
If values passed to a paragraph widget are not valid and contain a specific set of characters, applications are vulnerable to XSS attack against a user who opens a page on which a paragraph widget is rendered.
Versions of dynamic dashboard from v3.0.0 through v3.0.2 are affected.
Please upgrade to dynamic dashboard v3.0.2.
PoC
PoC will be published in a few weeks, once developers have had a chance to upgrade their apps.
Response
This vulnerability (in paragraph widget only) was reported by Raghav Sharma, who reported the issue and patched the issue during the morning of 05/10/2024. Thank you Raghav Sharma.
The review process concluded the same day at night, which revealed the issue was also present in paragraph widget. This was fixed the same day and dynamic dashboard v3.0.2 followed.
Note:
if you're published the view (blade files), you have to republish them or check the changes on release to update the affected file.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | lara-zeus/dynamic-dashboard | ≥ 3.0.0&&< 3.0.2 | 3.0.2 |
| 🐘Packagist | lara-zeus/artemis | ≥ 1.0.0&&< 1.0.7 | 1.0.7 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lara-zeus/dynamic-dashboard. 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 lara-zeus/dynamic-dashboard to 3.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c6cw-g7fc-4gwc 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-c6cw-g7fc-4gwc 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-c6cw-g7fc-4gwc. 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-c6cw-g7fc-4gwc in your dependencies?
O3 detects GHSA-c6cw-g7fc-4gwc across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.