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

> Authenticated users can inject scripts via Role or Organic Group names in the Drupal Maestro module, requiring an upgrade to fix.

- **Severity:** Low 3.5 (`AV:N/AC:M/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:** 13 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fm62-5w69-w9qp

## What is CVE-2014-8743?

CVE-2014-8743 is a low-severity cross-site scripting vulnerability in n/a, published on 13 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 Maestro module 7.x-1.x before 7.x-1.4 for Drupal allow remote authenticated users with certain permissions to inject arbitrary web script or HTML via a (1) Role or (2) Organic Group name.

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

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

It affects 1 product.


Products: Drupal Maestro.

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

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

## Is CVE-2014-8743 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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