VulnerabilityPublished 3 Jun 2025

CVE-2025-5513: quequnlong shiyi-blog · Cross-site Scripting

Affects quequnlong shiyi-blogSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 4.0 base score

5.1Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
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

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

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Jun 2025
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 26 Oct 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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
GitHubquequnlong/shiyi-blog`pkg:github/quequnlong/shiyi-blog`Other threats	Affected =1.2.0 =1.2.1	Fixed in–

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

AI-suggested

Since no official patches are available, European organizations should implement the following specific mitigations: 1) Employ Web Application Firewalls (WAFs) with custom rules to detect and block malicious script payloads targeting the /dev-api/api/comment/add endpoint. 2) Sanitize and validate all user inputs at the application level, especially the 'content' parameter, using strict whitelist-based filtering to remove or encode potentially dangerous characters. 3) Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers, reducing the impact of XSS attacks. 4) Monitor web application logs for unusual or suspicious comment submissions that may indicate exploitation attempts. 5) Educate users and administrators about the risks of clicking unknown links or interacting with untrusted content on the blog platform. 6) Consider disabling or restricting the comment functionality temporarily if feasible until a vendor patch or update is released. 7) Regularly review and update security controls and incident response plans to quickly detect and respond to potential exploitation.

Description

A vulnerability has been found in quequnlong shiyi-blog up to 1.2.1 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file /dev-api/api/comment/add. The manipulation of the argument content leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations using quequnlong shiyi-blog versions 1.2.0 or 1.2.1, this vulnerability poses a moderate risk primarily to web application users and administrators. Successful exploitation could lead to theft of user credentials, session tokens, or other sensitive information, potentially resulting in unauthorized access to user accounts or administrative functions. This could further lead to data breaches, defacement of websites, or distribution of malware through the compromised blog platform. Given the nature of XSS, the impact is often localized to the affected web application and its users but can have broader reputational and compliance consequences, especially under GDPR regulations concerning personal data protection. European organizations with public-facing blogs or community comment features using this software should be particularly cautious, as attackers could leverage this vulnerability to target customers or employees. The lack of vendor response and patches increases the urgency for organizations to implement compensating controls to mitigate risk.

Summary

CVE-2025-5513 is a cross-site scripting (XSS) vulnerability identified in the quequnlong shiyi-blog software, specifically affecting versions 1.2.0 and 1.2.1. The vulnerability exists in the /dev-api/api/comment/add endpoint, where the 'content' parameter is improperly sanitized or validated, allowing an attacker to inject malicious scripts. This flaw enables remote attackers to execute arbitrary JavaScript in the context of the victim's browser when viewing affected content, potentially leading to session hijacking, credential theft, or other malicious actions. The vulnerability is classified as problematic and has a CVSS 4.0 base score of 5.1, indicating a medium severity level. The attack vector is network-based (AV:N), requires low attack complexity (AC:L), no privileges (PR:L - low privileges), and user interaction (UI:P). The vulnerability impacts the confidentiality and integrity of user data by enabling script injection but does not directly affect availability. The vendor was notified but has not responded, and no patches or mitigations have been officially released. Although no known exploits in the wild have been reported yet, the public disclosure of the exploit code increases the risk of exploitation by threat actors. The vulnerability does not require authentication but does require some user interaction, such as a victim clicking a malicious link or viewing a compromised comment, to trigger the attack.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Jul 2025, 06:17 UTC

Technical details

References

Community reviews

Related threats