# CVE-2010-4240: Tiki Wiki CMS Groupware 5.2 has XSS


- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2019
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cx4x-r9pg-hrgx

## What is CVE-2010-4240?

CVE-2010-4240 is a medium-severity vulnerability in Tiki Tikiwiki Cms\/Groupware, published on 28 Oct 2019. 

### Official description

Tiki Wiki CMS Groupware 5.2 has XSS

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

## Which versions are affected by CVE-2010-4240?

It affects 1 product.


Products: Tiki Tikiwiki Cms\/Groupware.

## How do I fix CVE-2010-4240?

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

## Is CVE-2010-4240 being exploited?

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

## 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-2010-4240 and fix it if it is affected.

What it is: CVE-2010-4240 is a medium-severity vulnerability in Tiki Tikiwiki Cms\/Groupware, published on 28 Oct 2019. 
Exploitation: There is no known exploitation of CVE-2010-4240 in the wild and no public exploit code.

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-2010-4240/ (Markdown: https://insights.sbomify.com/CVE-2010-4240/index.md)
```

## Sources

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

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