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

> Authenticated users can inject scripts via the ticket URL field in the SupportEzzy Ticket System plugin, potentially compromising other users.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/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:** 2 Dec 2014
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-5rgg-g6jv-2fw3

## What is CVE-2014-9179?

CVE-2014-9179 is a medium-severity cross-site scripting vulnerability in n/a, published on 2 Dec 2014. 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 the SupportEzzy Ticket System plugin 1.2.5 for WordPress allows remote authenticated users to inject arbitrary web script or HTML via the "URL (optional)" field in a new ticket.

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

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

It affects 1 product.


Products: Supportezzy Ticket System Project Supportezzy Ticket System.

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

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

## Is CVE-2014-9179 being exploited?

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

Public exploit code:

- WordPress Plugin SupportEzzy Ticket System 1.2.5 - Persistent Cross-Site Scripting (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-9179 is a medium-severity cross-site scripting vulnerability in n/a, published on 2 Dec 2014. 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-2014-9179 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-9179/ (Markdown: https://insights.sbomify.com/CVE-2014-9179/index.md)
```

## Sources

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

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