dbcve.org
Beehive ForumApplication

CVE-2005-4460

MEDIUM · 5.1 CVSS v2.0 Published 2005-12-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/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
Cross-site scripting (XSS) vulnerability in Beehive Forum 0.6.2 and earlier allows remote attackers to inject arbitrary web script or HTML via the (1) Name, (2) Description, and (3) Comment fields to (a) links.php and (b) links_add.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

Stored cross-site scripting (XSS) vulnerability in Beehive Forum 0.6.2 and earlier allows remote attackers to inject arbitrary web script or HTML via the Name, Description, and Comment fields in links.php and links_add.php. User-supplied input is rendered without proper sanitization or output encoding.

MitigationImplement input validation and context-aware output encoding for all user-supplied data before rendering in HTML. Additionally, deploy a Content Security Policy (CSP) to mitigate XSS execution.

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
Beehive ForumApplication
Affected:= 0.1= 0.1.1= 0.2= 0.3= 0.3.1= 0.4= 0.5= 0.6.2= 0.6rc1= 0.6rc2

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
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 checks

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

  1. Confirm Beehive Forum installation
    Look for Beehive Forum software on the system. Check for the presence of characteristic files such as 'links.php' and 'links_add.php' in web-accessible directories, or search for Beehive Forum branding files like 'forum.php', 'index.php', or 'install.php'.
    Affected if Beehive Forum software is found on the system.
  2. Identify the installed Beehive Forum version
    Locate the version number from typical locations: a version file (often named 'version.php' or similar in the includes directory), the forum footer displayed on web pages, a README or CHANGELOG file in the installation directory, or the 'INSTALL' file. Compare the found version against the affected range: 0.1, 0.1.1, 0.2, 0.3, 0.3.1, 0.4, 0.5, 0.6.2, 0.6rc1, 0.6rc2.
    Affected if The installed version is 0.6.2 or earlier (including any 0.6rc version, 0.5, 0.4, 0.3.1, 0.3, 0.2, 0.1.1, or 0.1).
  3. Verify the links module is accessible
    Check if the 'links.php' and 'links_add.php' files exist in the web directory structure and are accessible via the web server. These files are required for the vulnerability to be exploitable.
    Affected if The links module files (links.php and links_add.php) exist and are web-accessible.
  4. Check for lack of output encoding in link submission forms
    Examine the source code of links.php and links_add.php for the Name, Description, and Comment input fields. Look for whether user-supplied data is echoed back to the page without htmlspecialchars(), htmlentities(), or similar encoding functions.
    Affected if The code renders user input from Name, Description, or Comment fields without proper sanitization or output encoding functions.

A user is affected if Beehive Forum version 0.6.2 or earlier is installed, the links module is accessible, and user input in the Name, Description, or Comment fields on links.php or links_add.php is rendered without output encoding.

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

Implement input validation and context-aware output encoding for all user-supplied data before rendering in HTML. Additionally, deploy a Content Security Policy (CSP) to mitigate XSS execution.

Fix this in Beehive Forum Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

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