CVE-2025-15454VulnerabilityPublished 5 Jan 2026Updated 23 Feb 2026

CVE-2025-15454: zhanglun lettura · Cross Site Scripting

Affects zhanglun letturaSource CVE Database V5

Not known to be exploited · CVSS 2.3 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

2.3Low

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

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

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

Base metrics

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: None
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: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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 5 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
zhanglunlettura	Affected =0.1.0 =0.1.1 =0.1.2 =0.1.3 =0.1.4 =0.1.5 =0.1.6 =0.1.7 =0.1.8 =0.1.9 =0.1.10 =0.1.11 =0.1.12 =0.1.13 =0.1.14 =0.1.15 =0.1.16 =0.1.17 =0.1.18 =0.1.19 =0.1.20 =0.1.21 =0.1.22	Fixed in–
GitHubzhanglun/lettura`pkg:github/zhanglun/lettura`Other threats	Affected <=0.1.22 =0.1.0 =0.1.1 =0.1.2 =0.1.3 =0.1.4 =0.1.5 =0.1.6 =0.1.7 =0.1.8 =0.1.9 =0.1.10 =0.1.11 =0.1.12 =0.1.13 =0.1.14 =0.1.15 =0.1.16 =0.1.17 =0.1.18 =0.1.19 =0.1.20 =0.1.21 =0.1.22	Fixed in–

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

AI-suggested

1. Immediately apply the official patch identified by commit 67213093db9923e828a6e3fd8696a998c85da2d4 to all affected lettura instances to remediate the vulnerability. 2. Conduct a thorough code review of the RSS Handler and related components to ensure proper input validation and output encoding, preventing similar XSS issues. 3. Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers accessing the application. 4. Educate users about the risks of interacting with untrusted content and encourage cautious behavior to reduce the impact of user interaction requirements. 5. Monitor application logs and network traffic for signs of attempted exploitation or anomalous behavior related to XSS attacks. 6. Consider deploying web application firewalls (WAFs) with rules tailored to detect and block XSS payloads targeting lettura. 7. Regularly update and patch all third-party components and dependencies to minimize exposure to known vulnerabilities.

Description

A vulnerability was detected in zhanglun lettura up to 0.1.22. This issue affects some unknown processing of the file src/components/ArticleView/ContentRender.tsx of the component RSS Handler. The manipulation results in cross site scripting. The attack can be executed remotely. This attack is characterized by high complexity. The exploitability is assessed as difficult. The exploit is now public and may be used. The patch is identified as 67213093db9923e828a6e3fd8696a998c85da2d4. It is best practice to apply a patch to resolve this issue.

Impact

The primary impact of CVE-2025-15454 is the potential for attackers to execute arbitrary scripts in the context of users interacting with the vulnerable lettura application. This can lead to session hijacking, unauthorized actions performed on behalf of users, defacement, or redirection to malicious sites. While the vulnerability does not directly compromise system availability or confidentiality at a high level, it undermines user trust and can facilitate further attacks such as phishing or credential theft. The high complexity and requirement for user interaction reduce the likelihood of widespread automated exploitation, but targeted attacks against organizations using lettura remain a concern. Organizations relying on lettura for RSS feed processing or content rendering may face reputational damage and operational disruption if exploited. The public availability of an exploit increases the urgency of patching to prevent opportunistic attacks.

Summary

CVE-2025-15454 identifies a cross-site scripting vulnerability in the zhanglun lettura software, versions up to 0.1.22. The vulnerability resides in the RSS Handler component, particularly in the source file src/components/ArticleView/ContentRender.tsx. The issue stems from improper sanitization or validation of input data processed by this component, allowing attackers to inject malicious scripts that execute in the context of the victim's browser. This XSS flaw can be exploited remotely without requiring authentication, but the attack complexity is high, and user interaction is necessary to trigger the malicious payload. The vulnerability impacts the confidentiality and integrity of user sessions and data, potentially enabling attackers to steal cookies, perform actions on behalf of users, or manipulate displayed content. The CVSS 4.0 vector indicates network attack vector, high attack complexity, no privileges required, user interaction required, and low impact on integrity with no impact on confidentiality or availability. Although the severity is rated low (2.3), the public availability of an exploit increases the risk profile. The vendor has released a patch identified by commit 67213093db9923e828a6e3fd8696a998c85da2d4, and applying this patch is the recommended remediation. No known active exploitation has been reported to date.

References

Community reviews

Loading reviews…