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

> Remote attackers can inject arbitrary scripts via crafted patches or admin pages in the Drupal PIFR module, 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:** 14 Oct 2014
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-c8gq-7jg7-j9p3

## What is CVE-2014-8765?

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

Multiple cross-site scripting (XSS) vulnerabilities in the Project Issue File Review module (PIFR) module 6.x-2.x before 6.x-2.17 for Drupal allow (1) remote attackers to inject arbitrary web script or HTML via a crafted patch, which triggers a PIFR client to test the patch and return the results to the PIFR_Server test results page or (2) remote authenticated users with the "manage PIFR environments" permission to inject arbitrary web script or HTML via vectors involving a PIFR_Server administrative page.

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

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

It affects 1 product.


Products: Drupal Project Issue File Review.

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

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

## Is CVE-2014-8765 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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