CVE-2006-1717
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 · uneditedCross-site scripting (XSS) vulnerability in newthread.php in MyBB (aka MyBulletinBoard) 1.10, when configured to permit new threads by unregistered users, allows remote attackers to inject arbitrary web script or HTML via the username.
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 confidenceA stored Cross-Site Scripting (XSS) vulnerability in MyBB 1.10's newthread.php allows remote attackers to inject arbitrary JavaScript or HTML through the username field when the forum is configured to permit new threads from unregistered users. The malicious payload is stored and executed when other users view the thread.
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
- High
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed MyBB versionAccess the MyBB admin control panel and navigate to Tools & Utilities > System Info, or check the version.php file in the inc/ directory. Alternatively, view the footer of the forum homepage for the version number.Affected if The installed version is exactly 1.10 (MyBB 1.10)
-
Verify if guest posting is enabled for new threadsLog out of the forum, navigate to the New Thread page (newthread.php), and attempt to post as a guest. Alternatively, check the admin control panel under Users & Permissions > Group Permissions > Registered > Can post new threads and verify that the Unregistered/Guest group has posting permissions enabled.Affected if Unregistered (guest) users are permitted to create new threads on the forum
-
Confirm the username field accepts arbitrary inputAs a guest, fill in the username field on newthread.php with a test string containing characters like < and >, then submit the thread. Check whether the raw input is stored and displayed in thread views without sanitization.Affected if The username from unregistered users is stored and rendered in thread views without being sanitized or encoded
-
Inspect database storage of usernamesAccess the MySQL database and query the mybb_threads table to examine how usernames from unregistered users (stored in the username column) are saved, or inspect the newthread.php code to see if username input is passed through any sanitization functions before database insertion.Affected if Usernames from unregistered users are stored in the database without sanitization (the raw input is preserved verbatim)
You are affected if you are running MyBB version 1.10 AND your forum permits unregistered users to create new threads, with the username field accepting and storing unsanitized input that gets rendered in thread views.
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 dataSanitize and properly encode the username field input from unregistered users before storing and rendering it. Apply context-aware output encoding when displaying usernames in thread views. Consider restricting thread creation to registered users only as a defense-in-depth measure.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-1717 — 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-1717 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