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

> Remote attackers can execute cross-site scripting attacks via the addto parameter in F*EX, requiring user interaction to trigger.

- **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:** Yes
- **Published:** 18 Jun 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-3877, GHSA-8g57-j3c3-fvfv

## What is CVE-2014-3877?

CVE-2014-3877 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Jun 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

Incomplete blacklist vulnerability in Frams' Fast File EXchange (F*EX, aka fex) before fex-20140530 allows remote attackers to conduct cross-site scripting (XSS) attacks via the addto parameter to fup.

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

It affects 1 product.


Products: Ulli Horlacher Fex.

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

Upgrade to a fixed version.

## Is CVE-2014-3877 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-3875](https://insights.sbomify.com/CVE-2014-3875/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2011-1409](https://insights.sbomify.com/CVE-2011-1409/): Auth bypass in n/a (medium 5.0)
- [CVE-2014-3876](https://insights.sbomify.com/CVE-2014-3876/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2012-0869](https://insights.sbomify.com/CVE-2012-0869/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2012-1293](https://insights.sbomify.com/CVE-2012-1293/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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