# CVE-2018-7932: Cross-site scripting in n/a

> Attackers can execute arbitrary JavaScript in Huawei AppGallery by tricking users into visiting malicious pages, bypassing whitelist mechanisms.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 24 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3x9p-x3q5-7j89

## What is CVE-2018-7932?

CVE-2018-7932 is a high-severity cross-site scripting vulnerability in n/a, published on 24 Apr 2018. 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

Huawei AppGallery versions before 8.0.4.301 has an arbitrary Javascript running vulnerability. An attacker may set up a malicious network environment and trick user into accessing a malicious web page to bypass the whitelist mechanism, which make the malicious Javascript loaded and run in the smart phone.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2018-7932?

It affects 1 product.


Products: Huawei Appgallery.

## How do I fix CVE-2018-7932?

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

## Is CVE-2018-7932 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-7931](https://insights.sbomify.com/CVE-2018-7931/): Security feature bypass in AppGallery (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7932 and fix it if it is affected.

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

## Sources

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

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