CVE-2024-12393: Drupal Core Cross-Site Scripting (XSS)

Published Dec 9, 2024
·
Updated

Drupal Core Cross-Site Scripting (XSS)

Other sources

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.

— GitHub

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.

— MITRE

Affected Software

21 affected componentsFixes available
Drupal Drupal>=8.8.0<10.2.11
Drupal Drupal>=10.3.0<10.3.9
Drupal Drupal>=11.0.0<11.0.8
composer/drupal/drupal>=11.0.0<11.0.8
11.0.8
composer/drupal/drupal>=10.3.0<10.3.9
10.3.9
composer/drupal/drupal>=8.8.0<10.2.11
10.2.11
composer/drupal/core-recommended>=11.0.0<11.0.8
11.0.8
composer/drupal/core-recommended>=10.3.0<10.3.9
10.3.9
composer/drupal/core-recommended>=8.8.0<10.2.11
10.2.11
composer/drupal/core>=11.0.0<11.0.8
11.0.8
composer/drupal/core>=10.3.0<10.3.9
10.3.9
composer/drupal/core>=8.8.0<10.2.11
10.2.11
composer/drupal/core>=11.0.0, <11.0.8
11.0.8
composer/drupal/core>=10.3.0, <10.3.9
10.3.9
composer/drupal/core>=8.8.0, <10.2.11
10.2.11
composer/drupal/core-recommended>=11.0.0, <11.0.8
11.0.8
composer/drupal/core-recommended>=10.3.0, <10.3.9
10.3.9
composer/drupal/core-recommended>=8.8.0, <10.2.11
10.2.11
composer/drupal/drupal>=11.0.0, <11.0.8
11.0.8
composer/drupal/drupal>=10.3.0, <10.3.9
10.3.9
composer/drupal/drupal>=8.8.0, <10.2.11
10.2.11

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/drupal/drupal to a version that resolves this vulnerability.

    Fixed in 11.0.8
  2. Upgrade

    Upgrade composer/drupal/drupal to a version that resolves this vulnerability.

    Fixed in 10.3.9
  3. Upgrade

    Upgrade composer/drupal/drupal to a version that resolves this vulnerability.

    Fixed in 10.2.11
  4. Upgrade

    Upgrade composer/drupal/core-recommended to a version that resolves this vulnerability.

    Fixed in 11.0.8
  5. Upgrade

    Upgrade composer/drupal/core-recommended to a version that resolves this vulnerability.

    Fixed in 10.3.9
  6. Upgrade

    Upgrade composer/drupal/core-recommended to a version that resolves this vulnerability.

    Fixed in 10.2.11
  7. Upgrade

    Upgrade composer/drupal/core to a version that resolves this vulnerability.

    Fixed in 11.0.8
  8. Upgrade

    Upgrade composer/drupal/core to a version that resolves this vulnerability.

    Fixed in 10.3.9
  9. Upgrade

    Upgrade composer/drupal/core to a version that resolves this vulnerability.

    Fixed in 10.2.11
  10. Upgrade

    Upgrade Drupal Core to a version that resolves this vulnerability.

    Fixed in 10.2.11
  11. Upgrade

    Upgrade Drupal Core to a version that resolves this vulnerability.

    Fixed in 10.3.9
  12. Upgrade

    Upgrade Drupal Core to a version that resolves this vulnerability.

    Fixed in 11.0.8

Event History

Dec 9, 2024
CVE Published
via MITRE·11:20 PM
Data Sourced
via MITRE·11:20 PM
DescriptionWeakness
Dec 10, 2024
Data Sourced
via NVD·12:15 AM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·12:31 AM
Data Sourced
via GitHub·12:31 AM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via Packagist·12:31 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-12393?

CVE-2024-12393 has a moderate severity rating due to the potential for improper input handling.

2

How do I fix CVE-2024-12393?

To fix CVE-2024-12393, upgrade your Drupal installation to versions 10.2.11, 10.3.9, or 11.0.8.

3

Which Drupal versions are affected by CVE-2024-12393?

CVE-2024-12393 affects Drupal Core versions from 8.8.0 before 10.2.11, from 10.3.0 before 10.3.9, and from 11.0.0 before 11.0.8.

4

What impact does CVE-2024-12393 have on my Drupal site?

The impact of CVE-2024-12393 can lead to the leakage of sensitive information if status messages are not properly sanitized.

5

Is it necessary to conduct a security audit after fixing CVE-2024-12393?

Yes, conducting a security audit after fixing CVE-2024-12393 is recommended to ensure that no other vulnerabilities exist.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203