CVE-2025-12279VulnerabilityPublished 27 Oct 2025

CVE-2025-12279: code-projects Client Details System · Cross Site Scripting

Affects code-projects Client Details SystemSource 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.2% chance of exploitation in 30 days – higher than 17% 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 27 Oct 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
GitHubhellonewbie/tutorial`pkg:github/hellonewbie/tutorial`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

Given the absence of official patches, European organizations should implement the following specific mitigations: 1) Conduct a thorough audit of all user input fields on the /welcome.php page and apply strict input validation to reject or sanitize suspicious characters and scripts. 2) Implement robust output encoding (e.g., HTML entity encoding) to neutralize any injected scripts before rendering content in browsers. 3) Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of XSS attacks. 4) Restrict user privileges and session lifetimes to minimize the window of opportunity for attackers. 5) Educate users about the risks of clicking untrusted links and encourage reporting of suspicious activity. 6) Monitor web server logs and application behavior for unusual patterns indicative of attempted XSS exploitation. 7) If feasible, isolate the vulnerable application behind a web application firewall (WAF) with rules targeting XSS payloads. 8) Plan for an upgrade or patch deployment as soon as the vendor releases a fix, and maintain an inventory of affected systems to ensure timely remediation. 9) Consider disabling or restricting access to the /welcome.php page if it is not essential. These measures go beyond generic advice by focusing on the specific vulnerable component and practical compensations in the absence of patches.

Description

A vulnerability has been found in code-projects Client Details System 1.0. This vulnerability affects unknown code of the file /welcome.php. Such manipulation leads to cross site scripting. The attack may be performed from remote. The exploit has been disclosed to the public and may be used.

Impact

For European organizations, the impact of CVE-2025-12279 depends on the extent of deployment of the code-projects Client Details System version 1.0. If used in customer-facing or internal portals, successful exploitation could lead to session hijacking, unauthorized actions performed on behalf of users, or phishing attacks leveraging the trusted domain. This can result in compromised user accounts, data integrity issues, and reputational damage. While the vulnerability does not directly affect system availability or confidentiality, the indirect effects of compromised user sessions can lead to data leakage or unauthorized access to sensitive information. Organizations in sectors with high regulatory requirements, such as finance, healthcare, or government, may face compliance risks if user data is compromised. The lack of known exploits reduces immediate risk, but public disclosure increases the likelihood of future attacks. European entities with limited security monitoring or outdated software inventories may be particularly vulnerable. The medium severity rating suggests prioritizing remediation but not immediate emergency response unless combined with other vulnerabilities.

Summary

CVE-2025-12279 is a cross-site scripting (XSS) vulnerability identified in the code-projects Client Details System version 1.0, specifically within the /welcome.php file. This vulnerability arises from improper input handling that allows an attacker to inject malicious scripts into web pages viewed by other users. The vulnerability can be exploited remotely without authentication, but requires user interaction to trigger the malicious payload, such as clicking a crafted link or visiting a manipulated page. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:H indicates high privileges required, but this conflicts with AT:N no authentication required, so likely a data inconsistency; given AT:N, no authentication is needed), user interaction required (UI:P), no impact on confidentiality (C:N), low impact on integrity (I:L), and no impact on availability (A:N). The vulnerability does not affect confidentiality or availability but may allow attackers to execute scripts in the context of the victim’s browser, potentially leading to session hijacking, phishing, or defacement. No known exploits are currently active in the wild, and no patches have been published yet. The vulnerability disclosure date is October 27, 2025, indicating recent discovery. The lack of CWE classification and patch links suggests early disclosure status. The vulnerability affects only version 1.0 of the product, which may limit exposure depending on the product’s deployment scale. The attack surface is limited to the /welcome.php page, which may be a common entry point for users. Given the nature of XSS, the primary risk is to end users rather than backend systems, but it can be leveraged as part of a broader attack chain.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 14:15 UTC

Technical details

References

Community reviews

Related threats