# CVE-2011-5267: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via parameters in the SpellChecker module, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Nov 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-3h3v-p275-5rjr

## What is CVE-2011-5267?

CVE-2011-5267 is a medium-severity cross-site scripting vulnerability in n/a, published on 5 Nov 2013. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in spell-check-savedicts.php in the SpellChecker module in Xinha, as used in WikiWig 5.01 and possibly other products, allow remote attackers to inject arbitrary web script or HTML via the (1) to_p_dict or (2) to_r_list parameter.  NOTE: this issue might be related to the htmlarea plugin and CVE-2013-5670.

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

## Which versions are affected by CVE-2011-5267?

It affects 1 product.


Products: Wikiwig Project Wikiwig.

## How do I fix CVE-2011-5267?

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

## Is CVE-2011-5267 being exploited?

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

Public exploit code:

- Xinha 0.96 - 'spell-check-savedicts.php' Multiple HTML Injection Vulnerabilities (exploitdb)
- WikiWig 5.01 - Multiple Cross-Site Scripting Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-5267 and fix it if it is affected.

What it is: CVE-2011-5267 is a medium-severity cross-site scripting vulnerability in n/a, published on 5 Nov 2013. Any signed-in user can exploit it over the network, 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-2011-5267 exists.

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

## Sources

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

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