# CVE-2005-3261: Information disclosure in n/a

> Remote attackers can obtain sensitive version information of installed scripts by directly requesting getversions.php in versatileBulletinBoard.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Oct 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rqrp-x7pw-rfgm

## What is CVE-2005-3261?

CVE-2005-3261 is a medium-severity vulnerability in n/a, published on 20 Oct 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

getversions.php in versatileBulletinBoard (vBB) 1.0.0 RC2 lists the versions of all installed scripts, which allows remote attackers to obtain sensitive information via a direct request.

## Which versions are affected by CVE-2005-3261?

It affects 1 product.


Products: Versatilebulletinboard Versatilebulletinboard.

## How do I fix CVE-2005-3261?

No fix has been published for CVE-2005-3261 yet. Limit exposure of the affected software until one is available.

## Is CVE-2005-3261 being exploited?

There is no known exploitation of CVE-2005-3261 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2003-1258](https://insights.sbomify.com/CVE-2003-1258/): Auth bypass in n/a (high 7.5)
- [CVE-2005-3259](https://insights.sbomify.com/CVE-2005-3259/): SQL injection in n/a (high 7.5)
- [CVE-2005-3260](https://insights.sbomify.com/CVE-2005-3260/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3261 and fix it if it is affected.

What it is: CVE-2005-3261 is a medium-severity vulnerability in n/a, published on 20 Oct 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-3261 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2005-3261/ (Markdown: https://insights.sbomify.com/CVE-2005-3261/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2005-3261
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2005-3261
- OSV: https://osv.dev/vulnerability/CVE-2005-3261

---
From sbomify Insights: https://insights.sbomify.com/CVE-2005-3261/
Summaries are generated and may contain mistakes; the official description above is the record.