dbcve.org
OpenbbApplication

CVE-2005-2566

HIGH · 7.5 CVSS v2.0 Published 2005-08-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Multiple SQL injection vulnerabilities in Open Bulletin Board (OpenBB) allow remote attackers to execute arbitrary SQL commands via the (1) FID parameter to board.php or (2) UID parameter to member.php.

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

OpenBB contains SQL injection vulnerabilities in board.php and member.php. The FID and UID parameters are not properly sanitized before being used in SQL queries, allowing attackers to inject arbitrary SQL commands. This could enable unauthorized data access, authentication bypass, or data manipulation.

MitigationSanitize user input in the FID and UID parameters using parameterized queries or prepared statements instead of string concatenation. Apply input validation and output encoding. Consider deploying a WAF as an additional layer of defense.

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
OpenbbApplication
Affected:all versions

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

AV:N/AC:L/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 checks

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

  1. Locate OpenBB installation files
    Search for board.php and member.php files in your web root directory. Common paths include /var/www/html/, /home/*/public_html/, or the document root of your web server.
    Affected if OpenBB files (board.php, member.php) are found on the server
  2. Identify the application version
    Check for a version file or examine header/meta tags in the OpenBB installation. Look for version.php, or check the footer/source code for version information.
    Affected if Any version of OpenBB is installed - the vulnerability affects all versions
  3. Examine board.php for FID parameter handling
    Open board.php and search for lines where the FID parameter is used in SQL queries. Look for patterns like $_GET['FID'] or $_POST['FID'] directly concatenated into SQL statements without sanitization functions like mysql_real_escape_string, parameterized queries, or prepared statements.
    Affected if The FID parameter is used in SQL queries without proper sanitization (parameterized queries, prepared statements, or escape functions)
  4. Examine member.php for UID parameter handling
    Open member.php and search for lines where the UID parameter is used in SQL queries. Look for patterns like $_GET['UID'] or $_POST['UID'] directly concatenated into SQL statements.
    Affected if The UID parameter is used in SQL queries without proper sanitization
  5. Test if parameters are accessible via HTTP
    Send a request to board.php?FID=1 or member.php?UID=1 and observe if the application processes these parameters. Use a tool like curl or browser developer tools to examine the response.
    Affected if The application accepts and processes FID or UID parameters without validation

If OpenBB is installed and the source code of board.php or member.php shows direct use of FID or UID parameters in SQL queries without sanitization, the environment is vulnerable to SQL injection.

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

Sanitize user input in the FID and UID parameters using parameterized queries or prepared statements instead of string concatenation. Apply input validation and output encoding. Consider deploying a WAF as an additional layer of defense.

Fix this in Openbb Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2005-2566 — 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-2005-2566 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