# CVE-2026-1152: technical-laohu mpay QR Code Image unrestricted upload

> Remote attackers can upload malicious files via the QR code image handler, potentially leading to code execution or privilege escalation.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jan 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-4662-2vgj-r5pw

## What is CVE-2026-1152?

CVE-2026-1152 is a medium-severity vulnerability in technical-laohu mpay, published on 19 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A security vulnerability has been detected in technical-laohu mpay up to 1.2.4. The impacted element is an unknown function of the component QR Code Image Handler. Such manipulation of the argument codeimg leads to unrestricted upload. The attack may be launched remotely. The exploit has been disclosed publicly and may be used.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-1152?

It affects 1 product.


Products: Technical-Laohu Mpay.

## How do I fix CVE-2026-1152?

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

## Is CVE-2026-1152 being exploited?

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

## Other vulnerabilities in technical-laohu mpay

- [CVE-2026-1153](https://insights.sbomify.com/CVE-2026-1153/): technical-laohu mpay cross-site request forgery (medium 5.3)
- [CVE-2026-1151](https://insights.sbomify.com/CVE-2026-1151/): technical-laohu mpay User Center cross site scripting (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1152 and fix it if it is affected.

What it is: CVE-2026-1152 is a medium-severity vulnerability in technical-laohu mpay, published on 19 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1152 exists.

Affected product: technical-laohu mpay. 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-2026-1152/ (Markdown: https://insights.sbomify.com/CVE-2026-1152/index.md)
```

## Sources

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

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