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

> Remote attackers can inject arbitrary web script or HTML via the content parameter in editText.php, potentially compromising user 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:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Jan 2015
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-f2vf-fwp8-754v

## What is CVE-2011-5317?

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

### Official description

Cross-site scripting (XSS) vulnerability in editText.php in WonderCMS before 0.4 allows remote attackers to inject arbitrary web script or HTML via the content parameter.

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

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

It affects 1 product.


Products: Wondercms Wondercms.

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

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

## Is CVE-2011-5317 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-35313](https://insights.sbomify.com/CVE-2020-35313/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2020-35314](https://insights.sbomify.com/CVE-2020-35314/): Code injection in n/a (critical 9.8)
- [CVE-2014-8704](https://insights.sbomify.com/CVE-2014-8704/): Path traversal in n/a (critical 9.8)
- [CVE-2014-8705](https://insights.sbomify.com/CVE-2014-8705/): Code injection in n/a (critical 9.8)
- [CVE-2024-32340](https://insights.sbomify.com/CVE-2024-32340/): Cross-site scripting in n/a (critical 9.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-5317 is a medium-severity cross-site scripting vulnerability in n/a, published on 1 Jan 2015. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-5317 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-2011-5317/ (Markdown: https://insights.sbomify.com/CVE-2011-5317/index.md)
```

## Sources

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

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