Security readout for executives and security teams
Plain-English summary
CVE-2026-1152 affects technical-laohu mpay versions 1.2.0 through 1.2.4. A QR code image upload path may accept unsafe files through the codeimg parameter. This could let an authenticated remote user upload content that harms confidentiality, integrity, or availability. Public exploit information exists, but the sources do not show confirmed active exploitation.
Executive priority
Treat this as a moderate-priority application risk. It is not confirmed as actively exploited, but public exploit disclosure increases urgency. Prioritize internet-facing or broadly accessible mpay deployments, especially if QR code image upload is enabled.
Technical view
The flaw is described as unrestricted upload in the mpay QR Code Image Handler, involving manipulation of the codeimg argument. VulDB maps it to CWE-434 and CWE-284. CVSS v2 is 5.8 with network access, low complexity, and multiple authentication required. A public issue is referenced as exploit disclosure; vendor fix details are not provided in the bundle.
Likely exposure
Organizations running technical-laohu mpay 1.2.0, 1.2.1, 1.2.2, 1.2.3, or 1.2.4 are potentially exposed. Risk is higher where mpay is reachable by untrusted users or where many authenticated users can access QR code image upload functionality.
Exploitation context
The vulnerability is remotely reachable and public exploit details have reportedly been disclosed. The CVSS vector indicates authentication is required. The provided sources do not include CISA KEV listing or other confirmation of active exploitation in the wild.
Researcher notes
Evidence is limited on the affected function and remediation. Do not assume remote unauthenticated exploitation; the CVSS v2 vector lists Au:M. Focus validation on version exposure, upload access controls, and whether codeimg handling permits unsafe file acceptance.
Mitigation direction
- Inventory mpay deployments and identify versions 1.2.0 through 1.2.4.
- Check technical-laohu project or vendor guidance for a fixed release or advisory.
- Restrict mpay access to trusted authenticated users where possible.
- Limit or disable QR code image upload if business operations allow.
- Monitor upload activity and investigate unexpected file types or locations.
Validation and detection
- Confirm the exact mpay version running in each environment.
- Verify whether QR code image upload is enabled and externally reachable.
- Review application logs for unusual codeimg upload activity.
- Check whether public-facing instances require authentication before upload access.
- Track vendor repositories and advisories for remediation status.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-1152 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.8 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:M/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
AV:N/AC:L/Au:M/C:P/I:P/A:P/E:POC/RL:ND/RC:UR6.46.4Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
5.8MediumVector: AV:N/AC:L/Au:M/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Source materials
- CVE List V5 sourceCVE List V5
- VDB-341745 | technical-laohu mpay QR Code Image unrestricted uploadCVE reference · vdb-entry, technical-description
- VDB-341745 | CTI Indicators (IOB, IOC, TTP, IOA)CVE reference · signature, permissions-required
- Submit #735775 | https://gitee.com/technical-laohu/mpay mpay v1.2.4 Arbitrary file upload vulnerabilityCVE reference · third-party-advisory
- https://github.com/bdkuzma/vuln/issues/17CVE reference · exploit, issue-tracking
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.