CVE-2023-33495
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 through 4.4.9 is vulnerable to HTML Injection.
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 through version 4.4.9 is vulnerable to HTML Injection, where improper sanitization of user-supplied input allows attackers to inject malicious HTML content into web pages.
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.4.9CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Determine installed Craft CMS versionCheck the version.php file in the craft folder or access the admin panel and look at the Craft CMS version displayed in the footer of the control panelAffected if The installed version is 4.4.9 or any earlier version (4.x <= 4.4.9)
-
Verify Craft CMS editionCheck whether you are running Craft Solo, Pro, or another edition by examining the config/app.php or the license key in the databaseAffected if Any Craft CMS edition running version 4.4.9 or earlier is affected
-
Identify user input entry pointsReview your templates and plugins for any fields that accept and display user-supplied input without additional sanitization, such as rich text fields, plain text fields, or custom fields in entry formsAffected if User-supplied input is displayed in templates without proper escaping or sanitization functions
-
Check for custom field configurationsExamine the field definitions in the Craft CMS control panel under Settings > Fields to identify text-based fields that accept end-user input and are used in public-facing formsAffected if Custom fields configured to accept raw user input are used in publicly accessible forms or displayed in front-end templates
Your Craft CMS installation is affected if it is running version 4.4.9 or any earlier 4.x version and displays user-supplied content without additional sanitization.
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 Craft CMS to a version newer than 4.4.9 (the latest stable release) to obtain the security fix.
Craft CMS 4.4.10 or later (latest 4.x stable release)
- 1. Backup your Craft CMS database and files before performing any upgrade.
- 2. Review the official Craft CMS changelog for version 4.4.10 or later to understand the security fix details.
- 3. Update Craft CMS to version 4.4.10 or the latest stable 4.x release by running composer update or using the control panel update feature.
- 4. Clear all caches after the upgrade to ensure the patched code is fully applied.
- 5. Verify the installation by checking the admin panel shows the new version number.
- 6. Test critical user-facing functionality to confirm the upgrade did not introduce issues.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33495 — 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-2023-33495 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