DrupalCMS
CVE-2024-55635
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 · uneditedImproper 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 7.0 before 7.102.
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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in Drupal Core where improper input neutralization allows malicious scripts to be injected into web pages. The vulnerability exists in Drupal Core versions 7.0 through 7.101 and enables attackers to execute arbitrary JavaScript in the context of a victim's browser.
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
>= 7.0, < 7.102CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Drupal Core versionLocate the CHANGELOG.txt file in the Drupal root directory and read the first few lines, or run the command: `drush status` or `grep 'VERSION' includes/bootstrap.inc`Affected if The version is 7.101 or lower (between 7.0 and 7.101 inclusive)
-
Confirm Drupal 7 branchCheck if the site is running Drupal 7 by examining the includes/bootstrap.inc file for the $base_version variable or checking the URL structure in settings.php for Drupal 7 pathsAffected if The site runs on Drupal 7.x branch (version begins with 7.)
-
Verify admin access existsAttempt to log into the Drupal admin dashboard at /?q=user or /user/login, or check if the user/1 account exists in the users tableAffected if Administrative accounts exist and can access content creation forms where XSS could be injected
You are affected if your Drupal Core installation version is 7.101 or lower (7.0 through 7.101 inclusive) and you have authenticated users with permission to create or edit content.
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 · scoped7.102
Upgrade Drupal Core to version 7.102 or later to resolve the XSS vulnerability. After upgrading, verify that custom modules and themes remain compatible.
Drupal 7.102
- Back up the Drupal database and all site files before proceeding
- Put the site into maintenance mode via Administration > Configuration > Development > Maintenance mode
- Download Drupal 7.102 from the official Drupal website (drupal.org/project/drupal)
- Extract the downloaded archive
- Replace the core Drupal files with the new version, ensuring to preserve the sites directory (containing settings.php and module/theme files)
- Run the update.php script by accessing yoursite.com/update.php in a browser
- Follow any on-screen instructions to complete the database updates
- Take the site out of maintenance mode
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Drupal
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-55635 — 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-2024-55635 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