CVE-2024-32003

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2024-04-12. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2024-1186 (ENISA EUVD) · GHSA-chcp-g9j5-3xxx (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

wn-dusk-plugin (Dusk plugin) is a plugin which integrates Laravel Dusk browser testing into Winter CMS. The Dusk plugin provides some special routes as part of its testing framework to allow a browser environment (such as headless Chrome) to act as a user in the Backend or User plugin without having to go through authentication. This route is [[URL]]/_dusk/login/[[USER ID]]/[[MANAGER]] - where [[URL]] is the base URL of the site, [[USER ID]] is the ID of the user account and [[MANAGER]] is the authentication manager (either backend for Backend, or user for the User plugin). If a configuration of a site using the Dusk plugin is set up in such a way that the Dusk plugin is available publicly and the test cases in Dusk are run with live data, this route may potentially be used to gain access to any user account in either the Backend or User plugin without authentication. As indicated in the README, this plugin should only be used in development and should *NOT* be used in a production instance. It is specifically recommended that the plugin be installed as a development dependency only in Composer. In order to remediate this issue, the special routes used above will now no longer be registered unless the APP_ENV environment variable is specifically set to dusk. Since Winter by default does not use this environment variable and it is not populated by default, it will only exist if Dusk's automatic configuration is used (which won't exhibit this vulnerability) or if a developer manually specifies it in their configuration. The automatic configuration performed by the Dusk plugin has also been hardened by default to use sane defaults and not allow external environment variables to leak into this configuration. This will only affect users in which the Winter CMS installation meets ALL the following criteria: 1. The Dusk plugin is installed in the Winter CMS instance. 2. The application is in production mode (ie. the debug config value is set to true in config/app.php). 3. The Dusk plugin's automatic configuration has been overridden, either by providing a custom .env.dusk file or by providing custom configuration in the config/dusk folder, or by providing configuration environment variables externally. 4. The environment has been configured to use production data in the database for testing, and not the temporary SQLite database that Dusk uses by default. 5. The application is connectable via the web. This issue has been fixed in version 2.1.0. Users are advised to upgrade.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 12, 2024

Last Modified

April 15, 2026

Advisory Details (2)

Auto-updated May 22, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Dusk plugin may allow unfettered user authentication in misconfigured installs · Advisory · wintercms/wn-dusk-plugin · GitHub

Affected: v2.1.0.

https://github.com/wintercms/wn-dusk-plugin/security/advisories/GHSA-chcp-g9j5-3xxx
Web page

wn-dusk-plugin/README.md at main · wintercms/wn-dusk-plugin · GitHub

https://github.com/wintercms/wn-dusk-plugin/blob/main/README.md

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composerwinter/wn-dusk-plugin @ 2.1.0 (fixes < 2.1.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
winter/wn-dusk-pluginv1.0.0, v2.0.0
  • every version up to 2.1.0: fixed in 2.1.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 94 of 238 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 6 repeat rows among the latest 100 are merged into the row they repeat. The 144 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-03 04:46 UTCEG score recompute
  2. 2026-11-03 04:46 UTCGHSA enrichmentGHSA-chcp-g9j5-3xxx · GitHub severity HIGH · GitHub CVSS 8.8
  3. 2026-11-02 16:40 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  4. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  5. 2026-11-01 08:14 UTCGHSA enrichmentGHSA-chcp-g9j5-3xxx · GitHub severity HIGH · GitHub CVSS 8.8
  6. 2026-11-01 08:14 UTCEG score recompute
  7. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  8. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  9. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  10. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  11. 2026-10-27 19:32 UTCEG score recompute
  12. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  13. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  14. 2026-10-25 17:12 UTCEG score recompute
  15. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  16. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  17. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  18. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  19. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  20. 2026-10-20 19:59 UTCEG score recompute
  21. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  22. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  23. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  24. 2026-10-18 07:17 UTCEG score recompute
  25. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
Show 69 more
  1. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  2. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  3. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  4. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  5. 2026-10-12 17:55 UTCEG score recompute
  6. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  7. 2026-10-11 21:20 UTCEG score recompute
  8. 2026-10-11 16:13 UTCEG score recompute
  9. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  10. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  11. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  12. 2026-10-08 17:07 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  13. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  14. 2026-10-07 14:05 UTCOSV refresh
  15. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  16. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  17. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  18. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  19. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  20. 2026-09-30 19:43 UTCEG score recompute
  21. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  22. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  23. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  24. 2026-09-27 13:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  25. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  26. 2026-09-26 00:23 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  27. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  28. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  29. 2026-09-22 14:46 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  30. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  31. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  32. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  33. 2026-09-17 20:20 UTCOSV refresh
  34. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  35. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  36. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  37. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  38. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  39. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  40. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  41. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  42. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  43. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  44. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  45. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  46. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  47. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  48. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  49. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  50. 2026-08-29 20:43 UTCOSV refresh
  51. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  52. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  53. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  54. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  55. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  56. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  57. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  58. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  59. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  60. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  61. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  62. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  63. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  64. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  65. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  66. 2026-08-13 07:35 UTCOSV refresh
  67. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  68. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  69. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.7% · 48th percentile

Frequently asked(5)

What is CVE-2024-32003?
CVE-2024-32003 is a high-severity vulnerability; its CVE record was published on April 12, 2024. wn-dusk-plugin (Dusk plugin) is a plugin which integrates Laravel Dusk browser testing into Winter CMS. The Dusk plugin provides some special routes as part of its testing framework to allow a browser environment (such as headless Chrome) to act as a user in the Backend or User plugin without…
When was the CVE record for CVE-2024-32003 published?
The CVE record for CVE-2024-32003 was published on April 12, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2024-32003 actively exploited?
CVE-2024-32003 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-32003?
CVE-2024-32003 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2024-32003?
A fix for CVE-2024-32003 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-32003

Explore →

Is Your Infrastructure Affected by CVE-2024-32003?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.