CVE-2022-37251
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 · uneditedCraft CMS 4.2.0.1 is vulnerable to Cross Site Scripting (XSS) via Drafts.
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 · moderate confidenceCraft CMS 4.2.0.1 contains a Cross Site Scripting (XSS) vulnerability in the Drafts functionality. The vulnerability allows attackers to inject malicious scripts through draft content, which then executes in the context of other users viewing those drafts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 4.2.0.1CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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.
-
Check installed Craft CMS versionLocate the composer.json file in your Craft CMS installation root and find the 'craftcms/cms' version entry, or run 'php craft --version' from the web root if Craft console commands are availableAffected if The version listed is exactly 4.2.0.1
-
Verify version via admin panelLog into the Craft CMS control panel and navigate to Utilities > System Report, or check the footer of any admin page which typically displays the version numberAffected if The displayed version is 4.2.0.1
-
Confirm Drafts module presenceDrafts are a core Craft CMS feature. Check if your installation has the drafts functionality by viewing the entry list in any section - drafts appear as separate entries with draft indicatorsAffected if You are running version 4.2.0.1 regardless of whether drafts are actively used, as the vulnerability exists in the code of that specific version
You are affected if your Craft CMS installation is exactly version 4.2.0.1, as this is the sole vulnerable version listed for this CVE.
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 the latest Craft CMS version to obtain the patch. Additionally, implement output encoding and input validation for all user-supplied content in Drafts functionality as a defense-in-depth measure.
Craft CMS 4.x (latest stable 4.x release, which includes the fix for this XSS vulnerability in Drafts)
- 1. Back up your entire Craft CMS installation including database before attempting any upgrade
- 2. Ensure you have a staging/development environment to test the upgrade first
- 3. Review the official Craft CMS upgrade guide at https://craftcms.com/docs/4.x/upgrade.html
- 4. Run the database backup and file backup
- 5. Update Craft CMS using Composer: run 'composer update craftcms/cms' or update your composer.json to specify a version constraint like '^4.2.0' and run 'composer update'
- 6. Clear all caches after upgrade via the control panel or CLI: 'php craft clear-caches/all'
- 7. Verify the upgrade was successful by checking the control panel footer shows the new version number
- 8. Test the Drafts functionality to ensure the XSS vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37251 — 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-2022-37251 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