# CVE-2023-50488: Code injection in n/a

> Attackers can execute arbitrary code on Blurams Lumi Security Cameras due to improper neutralization of special elements.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 2 Feb 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-cmx3-whxw-v8mp

## What is CVE-2023-50488?

CVE-2023-50488 is a critical code injection vulnerability in n/a, published on 2 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in Blurams Lumi Security Camera (A31C) v23.0406.435.4120 allows attackers to execute arbitrary code.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Blurams Lumi Security Camera A31c Firmware.

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

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

## Is CVE-2023-50488 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-51820](https://insights.sbomify.com/CVE-2023-51820/): Code injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-50488 is a critical code injection vulnerability in n/a, published on 2 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-50488 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-50488/ (Markdown: https://insights.sbomify.com/CVE-2023-50488/index.md)
```

## Sources

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

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