dbcve.org
Ckeditor 4Drupal extension · Cksource

CVE-2024-13245

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Drupal CKEditor 4 LTS - WYSIWYG HTML editor allows Cross-Site Scripting (XSS).This issue affects CKEditor 4 LTS - WYSIWYG HTML editor: from 1.0.0 before 1.0.1.

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 confidence

Stored Cross-Site Scripting (XSS) vulnerability in Drupal's CKEditor 4 LTS WYSIWYG editor allows authenticated users to inject malicious scripts through unsanitized HTML input. The vulnerability stems from improper input neutralization during web page generation, enabling script execution when other users view the crafted content.

MitigationUpgrade CKEditor 4 LTS module to version 1.0.1 or later which contains the patched version. If immediate patching is not possible, restrict editor permissions to trusted users only.

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
Ckeditor 4Drupal extension
Affected:= 1.0.0= 1.0.1

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify CKEditor 4 LTS module version
    Locate the Ckeditor 4 module in your Drupal installation and check its version number in the module's info file (ckeditor4.info.yml) or composer.json
    Affected if The installed version is 1.0.0 or 1.0.1 as listed in the affected versions
  2. Confirm CKEditor 4 is enabled and in use
    Verify that the CKEditor 4 module is enabled on your Drupal site and that it is configured as the default or active WYSIWYG editor for text formats (check at /admin/config/content/formats or via drush command)
    Affected if CKEditor 4 is enabled and configured as an active text editor
  3. Check for authenticated user access to content creation
    Review which user roles have permission to create or edit content that uses the CKEditor 4 WYSIWYG editor (check at /admin/people/permissions)
    Affected if Authenticated users have permissions to create or edit content using the CKEditor 4 editor
  4. Verify HTML input handling in text formats
    Inspect the text format configuration that uses CKEditor 4 to determine if HTML filtering is enabled and how restrictive the allowed HTML tags are (check at /admin/config/content/formats)
    Affected if The text format allows HTML input without sufficient sanitization of script-related tags or event attributes

You are affected if CKEditor 4 LTS version 1.0.0 or 1.0.1 is installed and enabled, and authenticated users can create or edit content using the CKEditor 4 WYSIWYG editor with HTML input capabilities.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade CKEditor 4 LTS module to version 1.0.1 or later which contains the patched version. If immediate patching is not possible, restrict editor permissions to trusted users only.

Recommended fix Moderate confidence

CKEditor 4 LTS module version 1.0.2 or later

  1. 1. Identify the CKEditor 4 LTS Drupal module version currently installed by checking the module's info.yml file or Drupal administration interface.
  2. 2. Navigate to the Drupal project page for CKEditor 4 LTS at www.drupal.org/project/ckeditor
  3. 3. Download the latest stable release of the CKEditor 4 LTS module (version 1.0.2 or later).
  4. 4. Back up your current Drupal site database and files.
  5. 5. Install the updated CKEditor 4 LTS module using Drupal's module management interface or via composer/Drush.
  6. 6. Clear Drupal caches to ensure the new version is fully loaded.
  7. 7. Verify the CKEditor 4 LTS module is updated by checking the version in the Drupal admin interface.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ckeditor 4 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13245 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-13245 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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