dbcve.org
Ubb.threadsApplication · Ubbcentral

CVE-2006-1423

MEDIUM · 5.0 CVSS v2.0 Published 2006-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
SQL injection vulnerability in showflat.php in UBB.threads 5.5.1, 6.0 br5, 6.0.1, 6.0.2, and earlier, allows remote attackers to execute arbitrary SQL commands via the Number parameter.

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 confidence

SQL injection vulnerability in showflat.php in UBB.threads allows remote attackers to execute arbitrary SQL commands via the Number parameter. This affects versions 5.5.1, 6.0 br5, 6.0.1, 6.0.2, and earlier.

MitigationProperly sanitize and validate the Number parameter input, and refactor database queries to use parameterized queries or prepared statements instead of dynamic SQL construction.

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
Ubb.threadsApplication
Affected:= 5.5.1= 6.0= 6.0.1= 6.0.2

CVSS 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
None
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/I:P/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate UBB.threads installation and identify version
    Check the version.php file in the UBB.threads root directory, or look for version indicators in the admin control panel under system information or version details.
    Affected if Version is 5.5.1, 6.0, 6.0.1, 6.0.2 or any earlier version (6.0 br5 falls in this range).
  2. Verify showflat.php exists
    Locate the showflat.php file within the UBB.threads installation directory structure, typically found in the main forum or scripts folder.
    Affected if The file showflat.php is present in the installation.
  3. Confirm web accessibility of showflat.php
    Attempt to access showflat.php via HTTP/HTTPS through the web server to confirm it is reachable and not removed or blocked.
    Affected if The file is accessible over the web, allowing the Number parameter to be manipulated in requests.

If the installed UBB.threads version is 5.5.1, 6.0, 6.0.1, 6.0.2 or earlier and showflat.php is web-accessible, the environment is vulnerable to SQL injection via the Number parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Properly sanitize and validate the Number parameter input, and refactor database queries to use parameterized queries or prepared statements instead of dynamic SQL construction.

Fix this in Ubb.threads Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-1423 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-1423 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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