VulnerabilityPublished 13 Nov 2026

CVE-2026-129142: itwanger paicoding · Cross-site Scripting

Affects itwanger paicodingSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.1 Medium.

Data as of 13 Nov 2026, 17:47 UTC

CVSS 4.0 base score

5.1Medium

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

Thin evidence

One scorer or none

CVSS scores by source
CNA (VulnCheck)	CVSS 4.0	5.1
CNA (VulnCheck)	CVSS 3.1	5.4

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

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

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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to 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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Subsequent System.
Subsequent 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 Subsequent 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.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 13 Nov 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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
itwangerpaicoding	Affected ≥ 766c48b39037970853af56f8d86dedbf7a8a2c1c, ≤ 903adce70309d340f7eec51ec3c80cfe3c8326c1	Fixed in–

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

AI-suggested

Until a fix is available, avoid viewing payment notifications from untrusted or suspicious payers and consider restricting who can initiate payments or set display names.

Description

CVE-2026-129142 is a stored cross-site scripting (XSS) vulnerability in the paicoding product by itwanger. The flaw occurs in the payment notifications feature, where the payer's display name is inserted without proper escaping and rendered unsafely in the notification HTML. Authenticated attackers can exploit this by setting a malicious display name and initiating a pending payment on a paid article, causing script execution in the author's browser when viewing notifications.

Impact

Successful exploitation allows an authenticated attacker to execute arbitrary scripts in the context of the author's browser when they view payment notifications. This can lead to session hijacking, unauthorized actions, or other client-side impacts depending on the attacker's payload. The CVSS 4.0 base score is 5.1, indicating a medium severity vulnerability with network attack vector, low complexity, and requiring user interaction.

Summary

The vulnerability exists in paicoding between commits 766c48b and 903adce. The NotifyMsgListener component inserts the payer's display name into payment notifications without escaping, and the notify-system-item.html template renders this input using th:utext, which does not escape HTML entities. This allows an authenticated attacker to craft a malicious display name and trigger stored XSS when the author views the notification, potentially leading to script execution in the author's browser context.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Nov 2026, 17:47 UTC

Technical details

References

Community reviews

Related threats