# CVE-2023-29752: Privilege escalation in n/a

> Unauthorized apps can escalate privileges by manipulating the Facemoji Emoji Keyboard component on Android devices.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Jun 2023
- **Updated:** 28 Jan 2025
- **Also known as:** GHSA-gw29-86rq-2225

## What is CVE-2023-29752?

CVE-2023-29752 is a high-severity vulnerability in n/a, published on 9 Jun 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An issue found in Facemoji Emoji Keyboard v.2.9.1.2 for Android allows unauthorized apps to cause escalation of privilege attacks by manipulating the component.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Ekatox Facemoji Emoji Keyboard.

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

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

## Is CVE-2023-29752 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-29752 is a high-severity vulnerability in n/a, published on 9 Jun 2023. It can only be exploited from the same machine or local network, 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-2023-29752 exists.

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-2023-29752/ (Markdown: https://insights.sbomify.com/CVE-2023-29752/index.md)
```

## Sources

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

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