# CVE-2017-20033: PHPList Reflected cross site scriting

> Remote attackers can execute arbitrary scripts in victims' browsers via a reflected XSS vulnerability in the admin interface of PHPList.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 Jun 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-jff2-f2xp-77cm

## What is CVE-2017-20033?

CVE-2017-20033 is a medium-severity cross-site scripting vulnerability in unspecified PHPList, published on 10 Jun 2022. 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

A vulnerability classified as problematic has been found in PHPList 3.2.6. This affects an unknown part of the file /lists/admin/. The manipulation of the argument page with the input send\'\";><script>alert(8)</script> leads to cross site scripting (Reflected). It is possible to initiate the attack remotely. Upgrading to version 3.3.1 is able to address this issue. It is recommended to upgrade the affected component.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

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

It affects 1 product.


Products: Phplist Phplist.

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

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

## Is CVE-2017-20033 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-20033 exists.

## Other vulnerabilities in unspecified PHPList

- [CVE-2020-22249](https://insights.sbomify.com/CVE-2020-22249/): File upload in n/a (critical 9.8)
- [CVE-2020-23361](https://insights.sbomify.com/CVE-2020-23361/): Auth bypass in n/a (critical 9.8)
- [CVE-2021-3188](https://insights.sbomify.com/CVE-2021-3188/): Other in n/a (critical 9.8)
- [CVE-2020-8547](https://insights.sbomify.com/CVE-2020-8547/): Auth bypass in n/a (critical 9.8)
- [CVE-2020-15072](https://insights.sbomify.com/CVE-2020-15072/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-20033 is a medium-severity cross-site scripting vulnerability in unspecified PHPList, published on 10 Jun 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-20033 exists.

Affected product: unspecified PHPList. 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-20033/ (Markdown: https://insights.sbomify.com/CVE-2017-20033/index.md)
```

## Sources

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

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