CVE-2026-1152
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceUnrestricted file upload vulnerability in the QR Code Image Handler component of technical-laohu mpay up to v1.2.4. The 'codeimg' parameter accepts arbitrary file uploads without proper validation, allowing attackers to upload malicious files (e.g., web shells) to the server. This is exploitable remotely with no authentication required.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.2.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed mpay versionLocate the application installation directory and check version file, or query the application API/interface for version informationAffected if The installed version is 1.2.4 or lower
-
Locate QR Code Image Handler componentSearch for files related to QR code handling - typically in modules, handlers, or components directories under the web application rootAffected if The QR Code Image Handler component exists and is accessible via web requests
-
Test upload endpoint accessibilitySend a POST request to the QR Code Image Handler endpoint with the 'codeimg' parameter containing a test file (e.g., a simple text file)Affected if The endpoint accepts file uploads without returning validation errors or rejecting the upload
-
Inspect web root for unauthorized uploadsSearch upload directories (often /uploads, /images, or /temp) for unexpected file types such as .php, .asp, .jsp, .exe, or other executable extensionsAffected if Suspicious executable files are found in upload directories, especially if they were not intentionally placed there
You are affected if technical-laohu mpay version 1.2.4 or lower is installed and the QR Code Image Handler component is accessible, as the unrestricted upload via the 'codeimg' parameter allows remote attackers to upload malicious files without authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately restrict upload functionality to validated file types (e.g., images only), implement server-side validation, rename uploaded files, store them outside webroot, and disable script execution in the upload directory. Consider disabling the affected component until a patch is available.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,024.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1152 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1152 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data