NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

CVE-2024-12393 — core

MEDIUMFix: drupal/core@276ac67

CVE-2024-12393 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in drupal/core. A fix is available for drupal/core — see the affected versions and patch details below.

Drupal core - Moderately critical - Cross Site Scripting - SA-CORE-2024-003

Also known asBIT-drupal-2024-12393DRUPAL-CORE-2024-003GHSA-8mvq-8h2v-j9vf
Published
Updated
Affected
9 pkgs
Patched
9 / 9
Exploits
None indexed
Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-12393.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs27th percentile — riskier than 27% of all scored CVEsHighest risk
0.00%1.07%2.14%3.21%2.5%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

9 pkgs affected
🐘drupal/core🐘drupal/core🐘drupal/core🐘drupal/core-recommended🐘drupal/core-recommended🐘drupal/core-recommended🐘drupal/drupal🐘drupal/drupal+1 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Drupal uses JavaScript to render status messages in some cases and configurations. In certain situations, the status messages are not adequately sanitized. 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.

Affected Packages

9 total 9 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistdrupal/core≥ 8.8.0&&< 10.2.1110.2.11composer require drupal/core:^10.2.11
🐘Packagistdrupal/core≥ 10.3.0&&< 10.3.910.3.9composer require drupal/core:^10.3.9
🐘Packagistdrupal/core≥ 11.0.0&&< 11.0.811.0.8composer require drupal/core:^11.0.8
🐘Packagistdrupal/core-recommended≥ 8.8.0&&< 10.2.1110.2.11composer require drupal/core-recommended:^10.2.11
🐘Packagistdrupal/core-recommended≥ 10.3.0&&< 10.3.910.3.9composer require drupal/core-recommended:^10.3.9
🐘Packagistdrupal/core-recommended≥ 11.0.0&&< 11.0.811.0.8composer require drupal/core-recommended:^11.0.8

Affected Products

1 product · 3 configurations
Application
drupaldrupal
≥ 11.0.0 && < 11.0.8
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update drupal/core to 10.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-12393 is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

Drupal uses JavaScript to render status messages in some cases and configurations. In certain situations, the status messages are not adequately sanitized. 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.
O3 Security · Impact-Aware SCA

Is CVE-2024-12393 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2024-12393: core — Fixed in 10.2.11