CVE-2006-1345
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 · uneditedpolls.php in MyBB (aka MyBulletinBoard) 1.10 allows remote attackers to obtain sensitive information via a vote action with an "option[]=null" parameter value, 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 confidencePath disclosure vulnerability in MyBB 1.10's polls.php where sending 'option[]=null' as a parameter triggers an error message revealing the full server filesystem path. This is an information disclosure issue allowing attackers to gather reconnaissance data about the server environment.
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.10CVSS 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.
-
Verify MyBB installation versionLocate the version file in your MyBB installation (typically version.php in the root directory or check the admin control panel under 'System' > 'Version Info'). Note the exact version number installed.Affected if The installed version is MyBB 1.10 exactly.
-
Locate polls.php fileFind the polls.php file within your MyBB installation directory. This is typically found in the root directory or in the '/inc/' folder depending on your MyBB version.Affected if The file exists and is part of the MyBB 1.10 installation.
-
Test parameter injection for path disclosureSend an HTTP GET or POST request to polls.php with the parameter 'option[]=null' (for example: polls.php?option[]=null or via a form submission). Capture the server response.Affected if The response contains a PHP error message or warning that displays the full server filesystem path (such as /home/user/public_html/...).
-
Inspect error message contentExamine any error output, warning messages, or exception details returned by the server. Look specifically for absolute directory paths that reveal the server's folder structure.Affected if Full absolute paths (beginning with / on Linux or C:\ on Windows) appear in the error output.
You are affected if you are running MyBB version 1.10 and submitting 'option[]=null' as a parameter to polls.php produces an error message that exposes the server's full filesystem 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 to a patched version of MyBB that addresses this vulnerability, or implement input validation to reject null/empty array parameters in polls.php before processing.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-1345 — 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-1345 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