CVE-2025-6353VulnerabilityPublished 20 Jun 2025Updated 23 Jun 2025

CVE-2025-6353: code-projects Responsive Blog · Cross Site Scripting

Affects code-projects Responsive BlogSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 25 Oct 2026, 19:02 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 30% 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/E:P

Base metrics

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

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: 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.
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 20 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 2026-10-25.

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
GitHubasd1238525/cve`pkg:github/asd1238525/cve`Other threats	Affected =1.0	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. Immediate implementation of input validation and output encoding on the 'keyword' parameter in /search.php to neutralize malicious scripts. 2. Deploy a Web Application Firewall (WAF) with custom rules to detect and block suspicious payloads targeting the search functionality. 3. Conduct a thorough security review of all user input handling in the Responsive Blog application to identify and remediate similar XSS vectors. 4. Educate users and administrators about the risks of clicking unknown links and encourage the use of browser security features that can mitigate XSS attacks, such as Content Security Policy (CSP). 5. Monitor web server logs for unusual query parameters or repeated attempts to exploit the 'keyword' parameter. 6. If possible, upgrade to a patched version once available or consider migrating to alternative blogging platforms with active security support. 7. Implement HTTP-only and Secure flags on cookies to reduce the impact of session hijacking attempts. 8. Regularly update and patch all web-facing applications and underlying infrastructure to minimize exposure to known vulnerabilities.

Description

A vulnerability classified as problematic was found in code-projects Responsive Blog 1.0. Affected by this vulnerability is an unknown functionality of the file /search.php. The manipulation of the argument keyword leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using the Responsive Blog 1.0 platform, this XSS vulnerability poses a moderate risk primarily to web application security and user trust. Attackers could exploit this flaw to conduct phishing attacks, steal session cookies, or perform actions on behalf of authenticated users, potentially leading to unauthorized access or data leakage. Organizations in sectors with high user interaction on blogs or content management systems—such as media, education, and e-commerce—may face reputational damage and regulatory scrutiny under GDPR if user data is compromised. While the vulnerability does not directly impact system availability or critical infrastructure, the indirect effects of successful exploitation, such as credential theft or injection of malicious content, could lead to broader security incidents. The lack of authentication requirement increases the attack surface, making it easier for remote attackers to target users. Given the medium severity and public disclosure, timely mitigation is essential to prevent exploitation, especially in environments where the Responsive Blog 1.0 is actively used.

Summary

CVE-2025-6353 is a cross-site scripting (XSS) vulnerability identified in version 1.0 of the code-projects Responsive Blog application, specifically within the /search.php file. The vulnerability arises from improper sanitization or validation of the 'keyword' parameter, which can be manipulated by an attacker to inject malicious scripts. This flaw allows an attacker to execute arbitrary JavaScript code in the context of the victim's browser when they access a crafted URL or interact with the vulnerable search functionality. The vulnerability is remotely exploitable without requiring authentication, but it does require some user interaction, such as clicking a malicious link or visiting a compromised page. The CVSS 4.0 base score is 5.1, indicating a medium severity level. The vector metrics indicate that the attack vector is network-based (AV:N), with low attack complexity (AC:L), no privileges required (PR:L suggests low privileges but some are needed), and user interaction is required (UI:P). The impact on confidentiality is none, integrity is low, and availability is none, meaning the primary risk is the execution of malicious scripts that can lead to session hijacking, defacement, or phishing attacks. No patches or fixes have been publicly linked yet, and no known exploits are currently observed in the wild, though the exploit details have been disclosed publicly, increasing the risk of exploitation in the near term.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Jun 2025, 12:37 UTC

Technical details

References

Community reviews

Related threats