# CVE-2023-41827: Cross-site scripting in Phones

> A local malicious app can inject HTML into the Motorola OTA update UI, potentially leading to code execution or security bypass.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Mar 2024
- **Updated:** 23 Aug 2024
- **Also known as:** GHSA-m5wr-8mcj-v838

## What is CVE-2023-41827?

CVE-2023-41827 is a medium-severity cross-site scripting vulnerability in Motorola Phones, published on 4 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An improper export vulnerability was reported in the Motorola OTA update application, that could allow a malicious, local application to inject an HTML-based message on screen UI.

Weakness: CWE-926 (Improper Export of Android Application Components)

## Which versions are affected by CVE-2023-41827?


## How do I fix CVE-2023-41827?

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

## Is CVE-2023-41827 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-41827 and fix it if it is affected.

What it is: CVE-2023-41827 is a medium-severity cross-site scripting vulnerability in Motorola Phones, published on 4 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-41827 in the wild and no public exploit code.

Affected product: Motorola Phones. 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-2023-41827/ (Markdown: https://insights.sbomify.com/CVE-2023-41827/index.md)
```

## Sources

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

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