# CVE-2004-1924: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via multiple parameters in TikiWiki, potentially stealing user data or hijacking sessions.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-8xcx-prh3-fqx7

## What is CVE-2004-1924?

CVE-2004-1924 is a medium-severity cross-site scripting vulnerability in Tiki Tikiwiki Cms\/Groupware, published on 10 May 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in Tiki CMS/Groupware (TikiWiki) 1.8.1 and earlier allow remote attackers to inject arbitrary web script or HTML via via the (1) theme parameter to tiki-switch_theme.php, (2) find and priority parameters to messu-mailbox.php, (3) flag, priority, flagval, sort_mode, or find parameters to messu-read.php, (4) articleId parameter to tiki-read_article.php, (5) parentId parameter to tiki-browse_categories.php, (6) comments_threshold parameter to tiki-index.php (7) articleId parameter to tiki-print_article.php, (8) galleryId parameter to tiki-list_file_gallery.php, (9) galleryId parameter to tiki-upload_file.php, (10) faqId parameter to tiki-view_faq.php, (11) chartId parameter to tiki-view_chart.php, or (12) surveyId parameter to tiki-survey_stats_survey.php.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Tiki Tikiwiki Cms\/Groupware.

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

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

## Is CVE-2004-1924 being exploited?

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

Public exploit code:

- TikiWiki < 1.8.1 - Multiple Vulnerabilities (exploitdb)
- TikiWiki Project 1.8 - 'tiki-switch_theme.php?theme' Cross-Site Scripting (exploitdb)
- TikiWiki Project 1.8 - 'messu-mailbox.php' Multiple Cross-Site Scripting Vulnerabilities (exploitdb)
- TikiWiki Project 1.8 - 'messu-read.php' Multiple Cross-Site Scripting Vulnerabilities (exploitdb)
- TikiWiki Project 1.8 - 'tiki-read_article.php?articleId' Cross-Site Scripting (exploitdb)
- TikiWiki Project 1.8 - 'tiki-browse_categories.php?parentId' Cross-Site Scripting (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-1924 and fix it if it is affected.

What it is: CVE-2004-1924 is a medium-severity cross-site scripting vulnerability in Tiki Tikiwiki Cms\/Groupware, published on 10 May 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1924 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-1924/ (Markdown: https://insights.sbomify.com/CVE-2004-1924/index.md)
```

## Sources

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

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