CVE-2021-41824
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 before 3.7.14 allows CSV 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 before version 3.7.14 is vulnerable to CSV injection, allowing attackers to embed malicious spreadsheet formulas (such as =CMD|'' or =SUM()) in exported CSV data that can execute arbitrary commands or exfiltrate data when users open the file in spreadsheet applications like Excel or Google Sheets.
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>= 3.4.0, < 3.7.14CVSS 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.
-
Determine installed Craft CMS versionCheck the version number in the control panel dashboard, or look in the file /composer.json for the 'version' field under 'require' (craftcms/cms), or run 'composer show craftcms/cms' from the command lineAffected if The version is 3.4.0 or higher but lower than 3.7.14
-
Verify CSV export feature is in useIdentify if any part of the application exports data to CSV format - check for custom plugins or templates that generate CSV exports, or review user activity for CSV download actionsAffected if CSV export functionality is enabled or custom exports exist in the environment
-
Check for untrusted user input in exportable dataReview what data gets exported to CSV - look for fields that accept user-generated content (comments, user profiles, entries with user-supplied fields) that could contain spreadsheet formula characters (=, +, -, @, tab, or carriage return)Affected if User-submitted content can appear in CSV exports without sanitization
The environment is affected if Craft CMS version is 3.4.0 or higher but lower than 3.7.14 AND the application exports any user-controlled data to CSV files.
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 · scoped3.7.14
Upgrade to Craft CMS 3.7.14 or later; if immediate patching is not feasible, implement input validation/sanitization on data exported to CSV and educate users about the risks of opening untrusted CSV files in spreadsheet applications.
Craft CMS 3.7.14 or later
- Backup your Craft CMS installation and database before upgrading
- Review the Craft CMS 3.7.14 release notes for any breaking changes or migration requirements
- Update Craft CMS to version 3.7.14 or later using your preferred method (composer, control panel, or CLI)
- After upgrading, verify that the CSV export functionality works correctly
- Test that the CSV injection vulnerability is no longer present by attempting to export data with formula-like content
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-41824 — 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-2021-41824 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