CVE-2006-4971
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 · uneditedMyBB (aka MyBulletinBoard) allows remote attackers to obtain sensitive information via a direct request for inc/plugins/hello.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 confidenceMyBB contains a direct request vulnerability in inc/plugins/hello.php that exposes the full server file system path in an error message to remote attackers. This information disclosure can aid further attacks by revealing installation details.
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= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0_final= 1.0_preview_release_2= 1.0_rc2= 1.1= 1.1.1= 1.1.2= 1.1.3= 1.1.4CVSS 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.
-
Identify MyBB installation versionLocate the MyBB version file - typically in inc/class_core.php or check the version shown in the admin panel under 'System' > 'Version Information'. Compare against affected versions: 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0_final, 1.0_preview_release_2, 1.0_rc2, 1.1, 1.1.1, 1.1.2, 1.1.3, 1.1.4Affected if Installed version matches any of the listed affected versions
-
Verify hello.php plugin file existsCheck if the file inc/plugins/hello.php exists in the MyBB web root directory. Use a file listing command or access the file directly via web browser to confirm presenceAffected if The file inc/plugins/hello.php exists on the server
-
Confirm PHP error display is enabledCheck the PHP configuration by creating a temporary phpinfo() script or reviewing php.ini for 'display_errors = On'. Also check web server configuration files (Apache httpd.conf, .htaccess) for PHP display_errors settingsAffected if display_errors is set to On (default or explicitly configured)
-
Test for path disclosureRequest the vulnerable URL directly: access http://[target]/inc/plugins/hello.php (or with .php extension) via HTTP. Alternatively, trigger any MyBB function that would cause hello.php to load and produce an errorAffected if The response contains the full server file system path (e.g., /home/user/public_html/inc/plugins/hello.php) in an error message
You are affected if your MyBB version is 1.0.1 through 1.1.4, the hello.php file exists in inc/plugins/, and PHP error display is enabled, causing path disclosure when the file is accessed.
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 dataRemove the hello.php file from the inc/plugins/ directory, or disable PHP error display (display_errors=Off) in php.ini and web server configuration to prevent path leakage.
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-4971 — 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-4971 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