CVE-2006-6373
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 · uneditedPhpMyAdmin 2.7.0-pl2 allows remote attackers to obtain sensitive information via a direct request for libraries/common.lib.php, which reveals the path in an error message.
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 confidencephpMyAdmin 2.7.0-pl2 contains a path disclosure vulnerability where directly requesting libraries/common.lib.php triggers an error message that reveals the server's absolute file system path. This information can aid attackers in reconnaissance for further exploitation.
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= 2.7.0_pl2CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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.
-
Locate phpMyAdmin installationSearch for phpMyAdmin directories on the web server, typically under document root paths like /var/www/html/, /www/, /htdocs/, or C:\inetpub\wwwroot\. Look for the presence of phpMyAdmin folders or files such as index.php, libraries/common.lib.php, or configuration files like config.inc.php.Affected if phpMyAdmin is found on the server
-
Identify phpMyAdmin versionCheck the version number by examining the login page source for a version string, or by finding a VERSION file in the phpMyAdmin root directory, or by inspecting the config.inc.php file for version-related comments.Affected if the installed version is exactly 2.7.0_pl2 (not newer or older versions)
-
Test direct access to vulnerable fileUsing a web browser or curl command, send an HTTP GET request directly to http://[hostname]/libraries/common.lib.php (or the equivalent path under the phpMyAdmin installation). Observe whether the page returns a PHP error message.Affected if accessing libraries/common.lib.php directly produces a PHP error or warning message
-
Confirm path disclosureExamine the error output from the previous step. Look for the server's absolute filesystem path in the error message, such as '/home/user/public_html/libraries/common.lib.php' or 'C:\inetpub\wwwroot\phpMyAdmin\libraries\common.lib.php'.Affected if the error message displays the absolute path to the file on the server filesystem
The environment is affected if phpMyAdmin version 2.7.0_pl2 is installed AND directly accessing libraries/common.lib.php reveals the server's absolute filesystem path in an error message.
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 dataUpgrade phpMyAdmin to a current version, or configure the web server to deny direct access to library/include files so they can only be accessed through the application's entry points.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-6373 — 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-2006-6373 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