# CVE-2017-5945: Cross-site scripting in n/a

> An attacker can execute arbitrary HTML and script code in a user's browser via the poodll_audio_url parameter in the PoodLL Filter plugin for Moodle.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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:** 10 Feb 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v4gf-fxjm-qp99

## What is CVE-2017-5945?

CVE-2017-5945 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 Feb 2017. 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

An issue was discovered in the PoodLL Filter plugin through 3.0.20 for Moodle. The vulnerability exists due to insufficient filtration of user-supplied data in the "poodll_audio_url" HTTP GET parameter passed to the "filter_poodll_moodle32_2016112802/poodll/mp3recorderskins/brazil/index.php" URL. An attacker could execute arbitrary HTML and script code in a browser in the context of the vulnerable website.

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

## Which versions are affected by CVE-2017-5945?

It affects 1 product.


Products: Poodll Moodle-Filter Poodll.

## How do I fix CVE-2017-5945?

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

## Is CVE-2017-5945 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5945 and fix it if it is affected.

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

## Sources

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

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