Lara-zeus Dynamic Dashboard and Artemis do not validate paragraph widget values which can be used for XSSGHSA-c6cw-g7fc-4gwc
MEDIUMFix: lara-zeus/artemis@3a3f9ddGHSA-c6cw-g7fc-4gwc is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in lara-zeus/dynamic-dashboard. A fix is available for lara-zeus/dynamic-dashboard — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-c6cw-g7fc-4gwc.
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
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.2composer require lara-zeus/dynamic-dashboard:^3.0.2 |
| 🐘Packagist | lara-zeus/artemis | ≥ 1.0.0&&< 1.0.7 | 1.0.7composer require lara-zeus/artemis:^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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
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 GHSA-c6cw-g7fc-4gwc in your dependencies?
Find it across Packagist, including transitive dependencies.