Vulnerability · CVE-2026-1151
A weakness has been identified in technical-laohu mpay up to 1.2.4.
Published Jan 19, 2026 · catalog updated Feb 23, 2026 · A weakness has been
Last checked Nov 6, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-1151. EPSS is 0.23%. Act only if a listed version of A weakness has been is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (A weakness has been).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-1153 · Medium
- CVE-2026-1152 · Medium
- Severity
- Medium4.8
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.23%
- Remediation
- Vendor / distro source
- Affected products
- vendor technical-laohu mpay 1.2.1
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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor technical-laohu mpay 1.2.11.2.1
How to fix CVE-2026-1151
No stored fix
No vendor fix text is stored. Use the linked advisory before you change production.
Version check
Seen in 1.2.1
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-1151. EPSS is 0.23%. Act only if a listed version of A weakness has been is installed.
Which versions are affected?
Compare what you have installed with technical-laohu mpay 1.2.1 1.2.1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.23%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Jan 19, 2026 · EUVD
Detected
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.
Feb 23, 2026 · EUVD
Updated
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.
Sources
- CVE.orgVulnerability recordCVE-2026-1151
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-1151
30-day exploitation probability 0.23%
first.org - EUVDVulnerability recordEUVD-2026-3230
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 av
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSNov 6, 2026
- CVE.orgNov 4, 2026
- EUVDNov 3, 2026