WordPressCMS
CVE-2006-3390
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 · uneditedWordPress 2.0.3 allows remote attackers to obtain the installation path via a direct request to various files, such as those in the (1) wp-admin, (2) wp-content, and (3) wp-includes directories, possibly due to uninitialized variables.
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 confidenceWordPress 2.0.3 contains an information disclosure vulnerability where direct HTTP requests to files in wp-admin, wp-content, or wp-includes directories expose the server's installation path. This occurs because PHP variables are not properly initialized before use, causing the path to be revealed in error messages or direct script output.
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
WordPressCMS
= 2.0.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
- 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.
-
Check WordPress versionLocate and read the wp-includes/version.php file, or access /wp-admin/about.php, or check the generator meta tag on any page sourceAffected if The version shown is exactly 2.0.3
-
Verify PHP display_errors is enabledCheck the PHP configuration file (php.ini) for 'display_errors = On' or run 'php -i | grep display_errors' or check via a PHP info pageAffected if display_errors is set to On (allowing error messages with full paths to be shown)
-
Test path disclosure in wp-adminSend a direct HTTP request to a non-existent file in wp-admin directory, e.g., GET /wp-admin/nonexistent.phpAffected if The response contains an error message revealing the server's full filesystem path
-
Test path disclosure in wp-includesSend a direct HTTP request to a non-existent file in wp-includes directory, e.g., GET /wp-includes/nonexistent.phpAffected if The response contains an error message revealing the server's full filesystem path
-
Test path disclosure in wp-contentSend a direct HTTP request to a non-existent file in wp-content directory, e.g., GET /wp-content/nonexistent.phpAffected if The response contains an error message revealing the server's full filesystem path
You are affected if running WordPress 2.0.3 with PHP display_errors enabled AND direct requests to wp-admin, wp-content, or wp-includes directories return error messages exposing the server's installation path.
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 WordPress to a current supported version. As an interim measure, configure PHP to disable display_errors and use .htaccess rules to prevent direct access to wp-admin, wp-content, and wp-includes directories.
Fix this in WordPress
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-3390 — 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-3390 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