# CVE-2016-4575: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML into Huawei smartphone email apps via malicious messages, potentially compromising user data.

- **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:** 25 May 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vfvr-qwmh-f4c8

## What is CVE-2016-4575?

CVE-2016-4575 is a medium-severity cross-site scripting vulnerability in n/a, published on 25 May 2016. 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

Cross-site scripting (XSS) vulnerability in the email APP in Huawei PLK smartphones with software AL10C00 before AL10C00B211 and AL10C92 before AL10C92B211; ATH smartphones with software AL00C00 before AL00C00B361, CL00C92 before CL00C92B361, TL00HC01 before TL00HC01B361, and UL00C00 before UL00C00B361; CherryPlus smartphones with software TL00C00 before TL00C00B553, UL00C00 before UL00C00B553, and TL00MC01 before TL00MC01B553; and RIO smartphones with software AL00C00 before AL00C00B360 allows remote attackers to inject arbitrary web script or HTML via an email message.

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

## Which versions are affected by CVE-2016-4575?

It affects 6 products.


Products: Huawei Ath, Huawei Ath Firmware, Huawei Cherryplus, Huawei Cherryplus Firmware, Huawei Plk Firmware, Huawei Rio Firmware.

## How do I fix CVE-2016-4575?

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

## Is CVE-2016-4575 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-4575 and fix it if it is affected.

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

## Sources

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

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