CVE-2026-1151VulnerabilityPublished 19 Jan 2026Updated 23 Feb 2026

CVE-2026-1151: technical-laohu mpay · Cross Site Scripting

Affects technical-laohu mpaySource CVE Database V5

Not known to be exploited · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
technical-laohumpay	Affected =1.2.0 =1.2.1 =1.2.2 =1.2.3 =1.2.4	Fixed in–
GitHubtechnical-laohu/mpay`pkg:github/technical-laohu/mpay`Other threats	Affected =1.2.0 =1.2.1 =1.2.2 =1.2.3 =1.2.4	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-1151, organizations should first verify if they are running affected versions (1.2.0 to 1.2.4) of technical-laohu mpay and prioritize upgrading to a patched version once available. In the absence of an official patch, implement strict input validation and output encoding on the Nickname parameter to neutralize malicious scripts. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in the browser context. Limit user privileges to the minimum necessary to reduce the risk of exploitation by high-privilege attackers. Educate users about the risks of clicking suspicious links or interacting with untrusted content. Monitor application logs for unusual activities related to the User Center component. Additionally, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block XSS payloads targeting the vulnerable parameter. Regularly review and update security controls to adapt to emerging threats.

Description

A weakness has been identified in technical-laohu mpay up to 1.2.4. The affected element is an unknown function of the component User Center. This manipulation of the argument Nickname causes cross site scripting. The attack may be initiated remotely. The exploit has been made available to the public and could be used for attacks.

Impact

The primary impact of CVE-2026-1151 is the potential compromise of user sessions and unauthorized actions within the technical-laohu mpay application. Successful exploitation can lead to theft of sensitive user information such as session tokens or personal data, enabling attackers to impersonate users or escalate privileges. This can result in financial fraud, unauthorized transactions, or data leakage. Additionally, injected scripts could be used to deliver malware or conduct phishing attacks targeting users of the platform. Organizations relying on technical-laohu mpay for payment processing or user management may face reputational damage, regulatory penalties, and operational disruptions if the vulnerability is exploited. The requirement for high privileges and user interaction somewhat limits the attack surface, but insider threats or compromised accounts could still be leveraged. The availability of a public exploit increases the risk of opportunistic attacks, especially in environments where patching is delayed.

Summary

CVE-2026-1151 is a cross-site scripting vulnerability affecting the User Center component of the technical-laohu mpay application, specifically versions 1.2.0 through 1.2.4. The vulnerability is triggered by manipulation of the Nickname parameter, which is not properly sanitized or encoded before being rendered in the web interface. This allows an attacker to inject arbitrary JavaScript code that executes in the context of the victim's browser. The attack vector is remote, but exploitation requires the attacker to have high privileges within the system and involves user interaction, such as a victim clicking a crafted link or viewing malicious content. The CVSS 4.0 base score is 4.8, reflecting medium severity due to the need for privileges and user interaction, with no impact on confidentiality or availability but some impact on integrity and limited impact on victim integrity. No authentication bypass or scope change is involved. Although no active exploits have been reported in the wild, a public exploit is available, which could facilitate targeted attacks. The vulnerability could be leveraged to steal session cookies, perform actions on behalf of the user, or deliver further malware payloads. The lack of official patches at the time of reporting necessitates immediate mitigation efforts by affected organizations.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 22:13 UTC

Technical details

References

Community reviews

Related threats