DrupalCMS
CVE-2007-5595
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 · uneditedCRLF injection vulnerability in the drupal_goto function in includes/common.inc Drupal 4.7.x before 4.7.8 and 5.x before 5.3 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via unspecified vectors.
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 confidenceCRLF injection vulnerability in Drupal's drupal_goto function allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks. The vulnerability exists in includes/common.inc for Drupal 4.7.x before 4.7.8 and 5.x before 5.3, where unsanitized user input in the redirect function can embed carriage return and line feed characters to split HTTP responses.
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
>= 4.7.0, < 4.7.8>= 5.0, < 5.3CVSS 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
- High
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:H/Au:N/C:P/I:P/A:P
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.
-
Identify installed Drupal versionCheck the CHANGELOG.txt file in the Drupal root directory for the version number, or log into the Drupal admin interface and navigate to Administer > Reports > Status report to view the Drupal version.Affected if Version is 4.7.0 to 4.7.7, or 5.0 to 5.2 (versions below 4.7.8 or 5.3)
-
Verify drupal_goto function is in useSearch the codebase for calls to drupal_goto function, which is a core redirect function commonly used throughout Drupal for page redirects. Check includes/common.inc where the function is defined.Affected if The drupal_goto function exists and is used for redirection within the site
-
Inspect vulnerable code in includes/common.incLocate the drupal_goto function definition in includes/common.inc. Examine the code that handles the $path parameter passed to the function. Look for absence of CRLF sanitization (removal or encoding of \r and \n characters) before constructing the Location header.Affected if The function does not sanitize or strip carriage return (\r) and line feed (\n) characters from user-controlled input before using it in HTTP redirects
-
Check for user-controlled input in redirectsReview how drupal_goto is called throughout the application. Identify any code paths where untrusted user input (such as query parameters, form submissions, or URL segments) flows into the $path argument of drupal_goto without prior sanitization.Affected if User-supplied data can reach the drupal_goto function without validation
The environment is affected if running Drupal versions 4.7.0 through 4.7.7 or 5.0 through 5.2, and the drupal_goto function in includes/common.inc lacks proper sanitization of CRLF characters in user-provided redirect paths.
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.
From vendor data4.7.85.3
Upgrade Drupal to version 4.7.8 or 5.3 or later. If upgrade is not possible, apply the vendor patch to sanitize input in the drupal_goto function to prevent CRLF character injection.
Fix this in Drupal
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5595 — 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-2007-5595 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