# CVE-2004-1923: Information disclosure in n/a

> Remote attackers can obtain sensitive web server path information via direct requests to specific PHP scripts in Tiki CMS.

- **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:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-4fwm-xx33-45wp

## What is CVE-2004-1923?

CVE-2004-1923 is a medium-severity vulnerability in Tiki Tikiwiki Cms\/Groupware, published on 10 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tiki CMS/Groupware (TikiWiki) 1.8.1 and earlier allows remote attackers to gain sensitive information via a direct request to (1) banner_click.php, (2) categorize.php, (3) tiki-admin_include_directory.php, (4) tiki-directory_search.php, which reveal the web server path in an error message.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2004-1923?

It affects 1 product.


Products: Tiki Tikiwiki Cms\/Groupware.

## How do I fix CVE-2004-1923?

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

## Is CVE-2004-1923 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1923 exists.

Public exploit code:

- TikiWiki < 1.8.1 - Multiple Vulnerabilities (exploitdb)
- TikiWiki Project 1.8 - 'categorize.php' Direct Request Full Path Disclosure (exploitdb)

## Other vulnerabilities in Tiki Tikiwiki Cms\/Groupware

- [CVE-2008-3653](https://insights.sbomify.com/CVE-2008-3653/): Multiple unspecified vulnerabilities in TikiWiki CMS/Groupware before 2.0 have unknown impact and attack vectors. (critical 10.0)
- [CVE-2007-6529](https://insights.sbomify.com/CVE-2007-6529/): Other in n/a (critical 10.0)
- [CVE-2010-4239](https://insights.sbomify.com/CVE-2010-4239/): Path traversal in CMS Groupware (critical 9.8)
- [CVE-2012-0911](https://insights.sbomify.com/CVE-2012-0911/): Deserialization in n/a (critical 9.8)
- [CVE-2025-34111](https://insights.sbomify.com/CVE-2025-34111/): Tiki Wiki <= 15.1 ELFinder Unauthenticated File Upload RCE (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1923 and fix it if it is affected.

What it is: CVE-2004-1923 is a medium-severity vulnerability in Tiki Tikiwiki Cms\/Groupware, published on 10 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1923 exists.

Affected product: Tiki Tikiwiki Cms\/Groupware. 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-2004-1923/ (Markdown: https://insights.sbomify.com/CVE-2004-1923/index.md)
```

## Sources

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

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