LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1151: technical-laohu mpay User Center cross site scripting

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.

MediumCVSS 4.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1151 is a cross-site scripting issue in technical-laohu mpay’s User Center. A privileged user can manipulate the Nickname field so another user who views it may trigger script execution. Business urgency is moderate: impact appears limited, but public exploit information exists and exposed admin/user-center workflows should be reviewed.

Executive priority

Treat as a near-term hygiene fix, not an emergency unless mpay User Center is exposed to many privileged users. Public exploit availability raises operational risk, but severity is moderated by high privilege and user-interaction requirements.

Technical view

Sources identify technical-laohu mpay 1.2.0 through 1.2.4 as affected. The vulnerable component is User Center, with the Nickname argument causing cross-site scripting, described by one advisory as stored XSS. CVSS v4 score is 4.8 with network attack vector, low complexity, high privileges required, and user interaction required.

Likely exposure

Organizations running technical-laohu mpay versions 1.2.0 to 1.2.4 are potentially exposed, especially where User Center is reachable by privileged accounts. Exposure is lower if mpay is not deployed, not internet-facing, or User Center access is tightly limited.

Exploitation context

The CVE record states the attack can be initiated remotely and public exploit material is available. There is no KEV listing and the provided sources do not state active exploitation in the wild. Exploitation appears to require high privileges and user interaction.

Researcher notes

Evidence is limited to CVE/VulDB-style records and a public issue reference. The affected function is unspecified. CWE-79 is consistent with XSS; CWE-94 is listed but not clearly explained in the provided description. No official patch or vendor advisory is identified in the supplied sources.

Mitigation direction

  • Identify any technical-laohu mpay deployments and confirm the installed version.
  • Check technical-laohu mpay vendor channels for a patched release or official workaround.
  • Restrict User Center access to trusted privileged users until remediation is confirmed.
  • Review and clean suspicious or unexpected Nickname values in existing accounts.
  • Apply output encoding or input validation if maintaining a local fork.

Validation and detection

  • Confirm whether mpay versions 1.2.0 through 1.2.4 are present.
  • Verify User Center Nickname values are safely encoded when displayed.
  • Review account-change logs for unusual Nickname updates.
  • Check whether public-facing instances expose User Center functionality.
  • Re-test after vendor update or local remediation.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 lookup
cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process 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 lookup
cve · low confidence lookup

CVE-2026-1151 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.8 (4.0)
Known Exploited
No
Published

Vector: 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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
4.8CVSS 4.0MediumCVSS: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——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

4.8Medium
CVSS 4.0 vector shape for CVE-2026-1151Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
technical-laohumpay1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.2.4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.