VulnerabilityPublished 3 Sep 2025

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

Affects code-projects Responsive Blog SiteSource CVE Database V5

Public exploit available · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

4.8Medium

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

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

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
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: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
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 3 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, 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
code-projects Responsive Blog Site	Affected =1.0	Fixed in–

AI-suggested

Given the absence of official patches, European organizations should implement immediate compensating controls. First, apply strict input validation and output encoding on all user-supplied data in the affected parameters (product_code, gen_name, product_name, supplier) to neutralize malicious scripts. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of XSS attacks. Web Application Firewalls (WAFs) should be configured with custom rules to detect and block suspicious payloads targeting the vulnerable parameters. Organizations should also conduct thorough code reviews and consider upgrading or replacing the vulnerable Responsive Blog Site software with a maintained and secure alternative. User awareness training can help mitigate risks from phishing attempts that may leverage this vulnerability. Finally, monitor web server logs for unusual requests targeting the vulnerable parameters to detect potential exploitation attempts early.

Description

A weakness has been identified in code-projects Responsive Blog Site 1.0. This affects an unknown function of the file blogs_view.php. Executing manipulation of the argument product_code/gen_name/product_name/supplier can lead to cross site scripting. It is possible to launch the attack remotely. The exploit has been made available to the public and could be exploited.

Impact

For European organizations using the code-projects Responsive Blog Site 1.0, this XSS vulnerability poses a risk primarily to the confidentiality and integrity of user sessions and data. Attackers could exploit this flaw to steal session cookies, impersonate users, or deliver malicious payloads to site visitors, potentially leading to credential theft or malware infections. Organizations operating in sectors with sensitive user data, such as e-commerce, finance, or healthcare, could face reputational damage and regulatory scrutiny under GDPR if user data is compromised. The vulnerability could also be leveraged to conduct targeted phishing campaigns or defacement attacks, undermining trust in the affected websites. Although the vulnerability does not directly impact system availability, the indirect consequences of successful exploitation could disrupt business operations and customer trust. The public availability of exploit code increases the urgency for mitigation, especially in environments where the affected software is exposed to the internet.

Summary

CVE-2025-9929 is a medium-severity cross-site scripting (XSS) vulnerability identified in version 1.0 of the code-projects Responsive Blog Site, specifically within the blogs_view.php file. The vulnerability arises from improper sanitization or validation of user-controllable input parameters such as product_code, gen_name, product_name, and supplier. An attacker can manipulate these parameters to inject malicious scripts that execute in the context of the victim's browser. The vulnerability is remotely exploitable without requiring authentication, but user interaction is necessary to trigger the malicious payload (e.g., by visiting a crafted URL). The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:H is unusual but likely a misclassification or means high privileges needed, but the description says remote exploitation without authentication), user interaction required (UI:P), and low impact on integrity and availability, with no impact on confidentiality. The exploit code has been publicly disclosed, increasing the risk of exploitation. However, there is no known exploitation in the wild reported yet, and no official patches or mitigations have been published by the vendor. This vulnerability allows attackers to perform XSS attacks that can lead to session hijacking, defacement, phishing, or distribution of malware by injecting malicious JavaScript into the vulnerable web pages viewed by other users.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Sep 2025, 22:03 UTC

Technical details

References

Community reviews

Related threats