# CVE-2006-0909: Information disclosure in n/a

> Remote attackers can view sensitive full path information via direct requests to multiple PHP scripts in Invision Power Board.

- **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:** 28 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r94f-5vgf-wccc

## What is CVE-2006-0909?

CVE-2006-0909 is a medium-severity vulnerability in n/a, published on 28 Feb 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Invision Power Board (IPB) 2.1.4 and earlier allows remote attackers to view sensitive information via a direct request to multiple PHP scripts that include the full path in error messages, including (1) PEAR/Text/Diff/Renderer/inline.php, (2) PEAR/Text/Diff/Renderer/unified.php, (3) PEAR/Text/Diff3.php, (4) class_db.php, (5) class_db_mysql.php, and (6) class_xml.php in the ips_kernel/ directory; (7) mysql_admin_queries.php, (8) mysql_extra_queries.php, (9) mysql_queries.php, and (10) mysql_subsm_queries.php in the sources/sql directory; (11) sources/acp_loaders/acp_pages_components.php; (12) sources/action_admin/member.php and (13) sources/action_admin/paysubscriptions.php; (14) login.php, (15) messenger.php, (16) moderate.php, (17) paysubscriptions.php, (18) register.php, (19) search.php, (20) topics.php, (21) and usercp.php in the sources/action_public directory; (22) bbcode/class_bbcode.php, (23) bbcode/class_bbcode_legacy.php, (24) editor/class_editor_rte.php, (25) editor/class_editor_std.php, (26) post/class_post.php, (27) post/class_post_edit.php, (28) post/class_post_new.php, (29) and post/class_post_reply.php in the sources/classes directory; (30) sources/components_acp/registration_DEPR.php; (31) sources/handlers/han_paysubscriptions.php; (32) func_usercp.php; (33) search_mysql_ftext.php, and (34) search_mysql_man.php in the sources/lib/ directory; and (35) convert/auth.php.bak, (36) external/auth.php, and (37) ldap/auth.php in the sources/loginauth directory.

## Which versions are affected by CVE-2006-0909?

It affects 1 product.


Products: Invision Power Services Invision Power Board.

## How do I fix CVE-2006-0909?

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

## Is CVE-2006-0909 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-7064](https://insights.sbomify.com/CVE-2006-7064/): Cross-site scripting in n/a (critical 9.3)
- [CVE-2007-3219](https://insights.sbomify.com/CVE-2007-3219/): Missing authorization in n/a (high 7.8)
- [CVE-2008-4171](https://insights.sbomify.com/CVE-2008-4171/): SQL injection in n/a (high 7.5)
- [CVE-2007-5688](https://insights.sbomify.com/CVE-2007-5688/): SQL injection in n/a (high 7.5)
- [CVE-2007-4913](https://insights.sbomify.com/CVE-2007-4913/): File upload in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0909 and fix it if it is affected.

What it is: CVE-2006-0909 is a medium-severity vulnerability in n/a, published on 28 Feb 2006. 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-2006-0909 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-2006-0909/ (Markdown: https://insights.sbomify.com/CVE-2006-0909/index.md)
```

## Sources

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

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