CVE-2025-6347VulnerabilityPublished 20 Jun 2025

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

Affects code-projects Responsive BlogSource CVE Database V5

Not known to be exploited · CVSS 4.8 Medium.

Data as of 25 Oct 2026, 19:02 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 28% 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 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
code-projects Responsive Blog	Affected =1.0 =1.12.4 =3.3.4	Fixed in–

AI-suggested

1. Immediate mitigation should include restricting access to the /responsive/resblog/blogadmin/admin/pageViewMembers.php page to trusted IP addresses or VPN users only, reducing exposure to remote attackers. 2. Implement strict Content Security Policy (CSP) headers to limit the execution of unauthorized scripts within the application context. 3. Employ web application firewalls (WAFs) with custom rules to detect and block typical XSS payload patterns targeting the vulnerable endpoint. 4. Conduct thorough input validation and output encoding on all user-supplied data in the affected page, focusing on HTML encoding to neutralize script injection vectors. 5. Monitor administrative user activity and logs for unusual behavior that may indicate exploitation attempts. 6. If possible, disable or limit the use of the affected Responsive Blog versions until a vendor patch is available. 7. Educate administrators and users about the risks of clicking on suspicious links or interacting with untrusted content, as user interaction is required for exploitation. 8. Regularly check for vendor updates or patches addressing this vulnerability and apply them promptly once released. 9. Consider migrating to alternative blogging platforms with active security support if the vendor does not provide timely fixes.

Description

A vulnerability was found in code-projects Responsive Blog 1.0/1.12.4/3.3.4. It has been declared as problematic. This vulnerability affects unknown code of the file /responsive/resblog/blogadmin/admin/pageViewMembers.php. The manipulation leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using code-projects Responsive Blog, this XSS vulnerability could lead to unauthorized script execution within the context of the affected web application. Potential impacts include theft of session cookies, enabling attackers to impersonate legitimate users, including administrators, which could lead to unauthorized changes or data exposure. Additionally, attackers could use the vulnerability to deliver phishing payloads or malware to users, undermining trust and potentially causing reputational damage. Given the administrative context of the vulnerable page, exploitation could facilitate further compromise of the blogging platform or connected systems. While the vulnerability requires high privileges and user interaction, organizations with multiple administrators or users accessing the admin interface are at increased risk. The impact is more pronounced for organizations relying on this platform for sensitive communications or internal collaboration. Disruption or compromise could affect operational continuity and data integrity. Furthermore, since the exploit is remotely initiable, attackers can target organizations without physical access, increasing the threat surface. The medium severity rating suggests moderate risk, but the lack of patches and public exploit code means organizations should proactively assess exposure and implement mitigations.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats