CVE-2024-32003
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedwn-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe wn-dusk-plugin for Winter CMS exposes special authentication bypass routes (_dusk/login/{userId}/{manager}) in production environments when the plugin is installed and its configuration is overridden. These routes allow unauthenticated attackers to impersonate any backend or user plugin account by specifying the user ID and authentication manager, enabling full account takeover.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the wn-dusk-plugin installationSearch for the Winter CMS Dusk plugin in your project's composer.json file under 'require' or 'require-dev', or check the vendor directory for wintercms/duskAffected if The plugin appears in the 'require' section of composer.json (not 'require-dev')
-
Identify the installed plugin versionRun 'composer show wintercms/dusk' or inspect the version listed in composer.lock to determine the exact version numberAffected if The installed version is earlier than 2.1.0 (versions prior to 2.1.0 contain the vulnerability)
-
Verify the plugin's presence in productionExamine your production environment's vendor directory or composer installation to confirm whether the dusk plugin code exists on the production serverAffected if The wn-dusk-plugin is installed in a production environment at all
-
Check for route accessibilityAttempt to access or probe for the route pattern _dusk/login/{userId}/{manager} on your Winter CMS backend, or inspect the registered routes in the applicationAffected if The _dusk/login routes are registered and accessible without authentication in the application
-
Review plugin configuration override settingsInspect the plugin's configuration files (config directory) for any overridden settings that may expose the bypass routes, particularly in production environmentsAffected if Configuration has been overridden from defaults in a way that exposes the authentication bypass routes
You are affected if the wn-dusk-plugin version is below 2.1.0 AND the plugin is present in a production environment with accessible _dusk routes.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to version 2.1.0 or later and ensure the Dusk plugin is only installed as a Composer development dependency (require-dev), never in production. Remove the plugin entirely from production environments.
2.1.0
- 1. Identify the winter-dusk-plugin in your Composer dependencies (likely in plugins/winter/dusk or via composer show winter/dusk-plugin).
- 2. Run `composer update winter/dusk-plugin` or specify the version: `composer require winter/dusk-plugin:2.1.0` to upgrade to the fixed release.
- 3. Clear any cached configurations by running `php artisan cache:clear` and `php artisan config:clear`.
- 4. Verify the version has been updated by checking `composer show winter/dusk-plugin` or your composer.lock file.
- 5. Test that the application functions correctly after the upgrade, particularly any Dusk-related testing functionality.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32003 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-32003 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data