# CVE-2014-5345: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via the step parameter in the Disqus Comment System plugin for WordPress.

- **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:** 19 Aug 2014
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vj6x-9f28-99g4

## What is CVE-2014-5345?

CVE-2014-5345 is a medium-severity cross-site scripting vulnerability in n/a, published on 19 Aug 2014. 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

Cross-site scripting (XSS) vulnerability in upgrade.php in the Disqus Comment System plugin before 2.76 for WordPress allows remote attackers to inject arbitrary web script or HTML via the step parameter.

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

## Which versions are affected by CVE-2014-5345?

It affects 1 product.


Products: Disqus Disqus Comment System.

## How do I fix CVE-2014-5345?

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

## Is CVE-2014-5345 being exploited?

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

Public exploit code:

- WordPress Plugin Disqus 2.7.5 - Cross-Site Request Forgery (Admin Persistent) / Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-5346](https://insights.sbomify.com/CVE-2014-5346/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2014-5347](https://insights.sbomify.com/CVE-2014-5347/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-5345 and fix it if it is affected.

What it is: CVE-2014-5345 is a medium-severity cross-site scripting vulnerability in n/a, published on 19 Aug 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-5345 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-2014-5345/ (Markdown: https://insights.sbomify.com/CVE-2014-5345/index.md)
```

## Sources

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

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