CVE-2006-6459
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 toplist.php in PhpBB Toplist 1.3.7 allows remote attackers to inject arbitrary HTML or web script via the (1) Name and (2) Information fields when adding a new site (toplistnew action).
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 confidencePhpBB Toplist 1.3.7 contains a stored cross-site scripting (XSS) vulnerability in toplist.php. The application fails to properly sanitize user-supplied input in the Name and Information fields when submitting a new site via the toplistnew action, allowing attackers to inject arbitrary HTML or JavaScript code that executes in the context of other users' browsers.
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.3.7CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Confirm PhpBB Toplist installationSearch the web root directory for the toplist.php file, typically found in the /modules/ or /toplist/ subdirectory of a PhpBB installationAffected if The toplist.php file exists in the PhpBB installation directory
-
Verify the installed versionOpen toplist.php in a text editor or use 'grep -i version' to locate the version declaration within the file header or a separate version fileAffected if The version is exactly 1.3.7
-
Check if toplistnew action is accessibleAttempt to access the toplist submission form via the URL pattern: /toplist.php?mode=toplistnew or /toplist.php?action=toplistnew (exact parameter depends on PhpBB version)Affected if The submission form loads without authentication or with low-privilege user access
-
Inspect input handling in toplist.phpExamine the toplist.php source code around the toplistnew mode handling, specifically looking for how $_POST['site_name'] and $_POST['info'] or similar fields are processed before database insertionAffected if No apparent input sanitization (htmlspecialchars, strip_tags, etc.) is applied to the Name and Information fields before storage
-
Verify stored XSS conditionSubmit a test entry with a benign payload like <script>alert('XSS')</script> in the Name or Information field, then view the toplist to see if the script executesAffected if The submitted payload renders as raw HTML/JavaScript and executes when the toplist page is viewed
You are affected if PhpBB Toplist version 1.3.7 is installed and the toplist submission form is accessible without proper input sanitization on the Name and Information fields.
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 dataImplement proper input validation and output encoding for all user-supplied fields, particularly the Name and Information parameters. Use context-appropriate encoding when rendering user input back to the browser, and consider implementing a Content Security Policy as a defense-in-depth measure.
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-6459 — 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-6459 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