dbcve.org
DrupalCMS

CVE-2024-12393

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-10
Fix available
A fix is available. Upgrade to 10.2.11 / 10.3.9 or later.
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 (XSS or 'Cross-site Scripting') vulnerability in Drupal Core allows Cross-Site Scripting (XSS).This issue affects Drupal Core: from 8.8.0 before 10.2.11, from 10.3.0 before 10.3.9, from 11.0.0 before 11.0.8.

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

A Cross-Site Scripting (XSS) vulnerability exists in Drupal Core where user-supplied input is not properly neutralized during web page generation. This allows authenticated attackers to inject malicious JavaScript or HTML into pages viewed by other users, potentially leading to session hijacking, credential theft, or defacement.

MitigationUpgrade Drupal Core to version 10.2.11, 10.3.9, or 11.0.8 or later to receive the security patch. If immediate upgrading is not possible, apply the official Drupal security patch for this issue.

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
DrupalCMS
Affected:>= 8.8.0, < 10.2.11>= 10.3.0, < 10.3.9>= 11.0.0, < 11.0.8

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. Determine installed Drupal Core version
    Check the version by viewing the VERSION constant in core/lib/Drupal.php, or run 'drush core:status' (if Drush is available), or access /admin/reports/status in the browser under the 'Drupal' row.
    Affected if Version is not shown or cannot be determined
  2. Compare version against affected ranges
    Review the version number found in the previous step against these vulnerable ranges: 8.8.0 through 10.2.10, 10.3.0 through 10.3.8, or 11.0.0 through 11.0.7.
    Affected if The installed version falls within any of these ranges
  3. Verify if patches are applied
    Inspect the codebase for any manually applied security patches related to this CVE, or check if the site is running a patched nightly/build version that would be newer than the affected ranges.
    Affected if No security patch has been applied and the version remains in the affected ranges

If the installed Drupal Core version is 8.8.0-10.2.10, 10.3.0-10.3.8, or 11.0.0-11.0.7 without a security patch applied, the environment is vulnerable to the XSS flaw.

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
Upgrade available Upgrade to 10.2.11 / 10.3.9 / 11.0.8 or later
Fixed in 10.2.1110.3.911.0.8
Interim mitigation

Upgrade Drupal Core to version 10.2.11, 10.3.9, or 11.0.8 or later to receive the security patch. If immediate upgrading is not possible, apply the official Drupal security patch for this issue.

Recommended fix High confidence

Upgrade to Drupal 10.2.11+, 10.3.9+, or 11.0.8+ depending on your current major branch

  1. Backup the Drupal database and files
  2. Verify current Drupal version with composer show drupal/core or within the Drupal admin UI
  3. Upgrade Drupal Core to a fixed version: for 10.2.x line upgrade to 10.2.11 or later, for 10.3.x line upgrade to 10.3.9 or later, for 11.x line upgrade to 11.0.8 or later (use composer require drupal/core:^10.3.9 --with-all-dependencies or similar)
  4. Run database updates via drush updatedb or via the update.php script
  5. Clear all Drupal caches (drush cr)
Caveat Minor version upgrades in Drupal typically have minimal breaking changes; always review the release notes for any deprecated APIs or configuration changes before upgrading

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

Fix this in Drupal Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12393 — 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-12393 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