# CVE-2026-1153: technical-laohu mpay cross-site request forgery

> Remote attackers can perform cross-site request forgery attacks against the mpay web application, potentially bypassing security controls.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **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:** 19 Jan 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-jg8v-v78g-vjrq

## What is CVE-2026-1153?

CVE-2026-1153 is a medium-severity vulnerability in technical-laohu mpay, published on 19 Jan 2026. 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

A vulnerability was detected in technical-laohu mpay up to 1.2.4. This affects an unknown function. Performing a manipulation results in cross-site request forgery. Remote exploitation of the attack is possible. The exploit is now public and may be used.

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Technical-Laohu Mpay.

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

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

## Is CVE-2026-1153 being exploited?

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

## Other vulnerabilities in technical-laohu mpay

- [CVE-2026-1152](https://insights.sbomify.com/CVE-2026-1152/): technical-laohu mpay QR Code Image unrestricted upload (medium 5.1)
- [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-1153 and fix it if it is affected.

What it is: CVE-2026-1153 is a medium-severity vulnerability in technical-laohu mpay, published on 19 Jan 2026. An attacker can exploit it over the internet without logging in, 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-2026-1153 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-1153/ (Markdown: https://insights.sbomify.com/CVE-2026-1153/index.md)
```

## Sources

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

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