dbcve.org
phpMyAdminApplication

CVE-2006-6374

HIGH · 7.5 CVSS v2.0 Published 2006-12-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Multiple CRLF injection vulnerabilities in PhpMyAdmin 2.7.0-pl2 allow remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in a phpMyAdmin cookie in (1) css/phpmyadmin.css.php, (2) db_create.php, (3) index.php, (4) left.php, (5) libraries/session.inc.php, (6) libraries/transformations/overview.php, (7) querywindow.php, (8) server_engines.php, and possibly other files.

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

CRLF injection vulnerability in phpMyAdmin 2.7.0-pl2 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in phpMyAdmin cookies. The vulnerability affects multiple files including index.php, session.inc.php, and other PHP scripts that process cookie values without proper sanitization.

MitigationUpgrade to a patched version of phpMyAdmin; if upgrading is not feasible, implement strict input validation to strip CRLF sequences from all cookie values before processing in affected files.

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
phpMyAdminApplication
Affected:= 2.7.0_pl2

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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed phpMyAdmin version
    Locate the phpMyAdmin version file (usually version.php in the root directory or check the meta tags in index.php), or access phpMyAdmin and look for the version number typically displayed on the main login page footer
    Affected if The installed version is exactly 2.7.0-pl2 (note: underscore vs hyphen may vary in display)
  2. Locate cookie processing code in index.php
    Open the index.php file in the phpMyAdmin installation directory and search for $_COOKIE variable usage, specifically looking for lines that assign cookie values to variables without sanitization
    Affected if Cookie values from $_COOKIE are being used directly in headers or output without filtering CRLF (\r\n) sequences
  3. Inspect session.inc.php for cookie handling
    Open session.inc.php (or libraries/session.inc.php depending on directory structure) and examine how cookie values are processed, particularly looking for assignments like $cookie[...]=... or $_COOKIE[...], and check if any stripslashes or similar functions are applied without CRLF removal
    Affected if The code processes cookie values but does not contain logic to strip or reject CRLF characters (\r and \n) before using them in HTTP contexts
  4. Check other PHP scripts for similar patterns
    Search the phpMyAdmin directory for files containing $_COOKIE usage (using grep or similar: grep -r '\$_COOKIE' *.php) and examine each to see if cookie values are used in any output, headers, or logged without CRLF sanitization
    Affected if Any PHP script processes cookie values without removing or rejecting CRLF sequences before using them in HTTP responses

You are affected if your phpMyAdmin installation is version 2.7.0-pl2 AND any of your PHP scripts handle cookie values without filtering out CRLF (\r\n) characters before using them in HTTP contexts.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of phpMyAdmin; if upgrading is not feasible, implement strict input validation to strip CRLF sequences from all cookie values before processing in affected files.

Fix this in phpMyAdmin Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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