VulnerabilityPublished 31 Dec 2025Updated 2 Jan 2026

CVE-2025-15223: Philipinho Simple-PHP-Blog · Cross-site Scripting

Affects Philipinho Simple-PHP-BlogSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

5.3Medium

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:N/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: 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: 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: 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 31 Dec 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

AI-suggested

To mitigate CVE-2025-15223, organizations should implement strict input validation and output encoding on all user-supplied data, especially the Username parameter in /login.php, to neutralize malicious scripts. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. Regularly update the Simple-PHP-Blog software to the latest commits, monitoring the vendor’s repository or community channels for patches or security advisories. Conduct security testing, including automated scanning and manual code reviews, to identify and remediate similar vulnerabilities. Educate users about phishing risks and suspicious links to reduce the likelihood of successful exploitation. For environments where the software is not critical, consider replacing it with more secure, actively maintained blogging platforms. Finally, monitor web server logs and application behavior for signs of exploitation attempts.

Description

A vulnerability was found in Philipinho Simple-PHP-Blog up to 94b5d3e57308bce5dfbc44c3edafa9811893d958. Impacted is an unknown function of the file /login.php. Performing manipulation of the argument Username results in cross site scripting. The attack is possible to be carried out remotely. The exploit has been made public and could be used. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The vendor was contacted early about this disclosure and makes clear that the product is "[f]or educational purposes only".

Impact

For European organizations, the primary impact of this vulnerability is the potential compromise of user sessions and credentials through XSS attacks, which can lead to unauthorized access, data theft, or manipulation of user interactions. Educational institutions or small organizations using the Simple-PHP-Blog platform for internal or public-facing blogs may face reputational damage and loss of user trust if exploited. The vulnerability could also serve as a foothold for further attacks within a network if attackers leverage stolen credentials or session tokens. Although the product is labeled for educational use, some organizations might deploy it in low-risk environments, increasing the attack surface. The remote exploitability without authentication and the public availability of exploit code heighten the risk of opportunistic attacks. However, the medium severity score indicates that the impact is somewhat contained, primarily affecting confidentiality and integrity of user data rather than system availability or broader network compromise.

Summary

CVE-2025-15223 is a cross-site scripting (XSS) vulnerability identified in the Philipinho Simple-PHP-Blog application, specifically affecting the /login.php file. The vulnerability arises from improper handling of the Username parameter, allowing an attacker to inject malicious JavaScript code that executes in the context of the victim's browser. This flaw is exploitable remotely without any authentication or privileges, requiring only user interaction to trigger the payload, such as clicking a crafted link or visiting a malicious page. The product uses a rolling release strategy, which means that affected versions cannot be precisely enumerated beyond the specified commit hash. The vendor has been notified and clarifies that the software is intended for educational use, which may limit its deployment in production environments. The CVSS 4.0 base score is 5.3, reflecting medium severity due to the lack of privilege requirements and ease of exploitation, but limited impact on confidentiality and availability. No patches or updates have been explicitly linked, and no active exploitation has been reported. The vulnerability could enable attackers to steal session cookies, perform phishing attacks, or deface web content by injecting scripts that run in users' browsers. Given the public availability of exploit code, organizations using this software should consider immediate remediation steps to prevent abuse.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 7 Jan 2026, 03:26 UTC

Technical details

References

Community reviews

Related threats