CVE-2025-12281VulnerabilityPublished 27 Oct 2025

CVE-2025-12281: 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 16% 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
code-projects Client Details System	Affected =1.0	Fixed in–

AI-suggested

1. Immediate mitigation should include implementing strict input validation and output encoding on all user-supplied data within /admin/clientview.php to prevent script injection. 2. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in the administrative interface. 3. Restrict access to the admin panel by IP whitelisting or VPN-only access to reduce exposure. 4. Educate administrators about phishing risks and suspicious links to minimize user interaction exploitation. 5. Monitor logs for unusual activity or access patterns indicative of exploitation attempts. 6. If possible, isolate the Client Details System from other critical systems to limit lateral movement. 7. Engage with the vendor or community to obtain or develop patches and apply them promptly once available. 8. Consider deploying Web Application Firewalls (WAF) with custom rules to detect and block XSS payloads targeting this endpoint. 9. Regularly audit and update all third-party components and dependencies used by the system to reduce attack surface.

Description

CVE-2025-12281 is a medium severity cross-site scripting (XSS) vulnerability in version 1.0 of the code-projects Client Details System, specifically in the /admin/clientview.php file. The vulnerability allows remote attackers to execute malicious scripts due to insufficient input sanitization, potentially leading to user session hijacking or defacement. Exploitation does not require authentication but does require user interaction. Although the exploit has been publicly disclosed, no known active exploitation in the wild has been reported. The vulnerability impacts confidentiality and integrity to a limited extent and does not affect availability. European organizations using this software should prioritize patching or applying mitigations to prevent potential targeted attacks. Countries with higher adoption of this product or with strategic interest in client data management systems are more likely to be affected.

Impact

For European organizations, this vulnerability poses a moderate risk primarily to the confidentiality and integrity of administrative sessions within the affected Client Details System. Exploitation could lead to unauthorized access to client data, manipulation of client records, or unauthorized administrative actions. This can result in data breaches, loss of customer trust, and regulatory non-compliance, especially under GDPR requirements. The impact on availability is negligible, but the potential for lateral movement or further exploitation following session hijacking could escalate the threat. Organizations using this software in sectors such as finance, healthcare, or legal services—where client data is highly sensitive—face increased risk. The medium severity rating reflects the need for timely mitigation but indicates that the vulnerability is not trivially exploitable at scale without user interaction.

Summary

CVE-2025-12281 identifies a cross-site scripting (XSS) vulnerability in the code-projects Client Details System version 1.0, specifically within the /admin/clientview.php file. The vulnerability arises from improper input validation or output encoding, allowing attackers to inject malicious scripts that execute in the context of an authenticated administrator's browser session. This flaw can be exploited remotely without authentication, though it requires user interaction, such as clicking a crafted link or viewing a manipulated page. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:H but with user interaction UI:P), and limited impact on confidentiality and integrity (CI:L) with no impact on availability. The vulnerability could enable attackers to steal session cookies, perform actions on behalf of the administrator, or conduct phishing attacks within the administrative interface. Although no patches or official fixes have been published yet, the public disclosure of the exploit increases the risk of exploitation. The absence of known active exploitation in the wild suggests limited current impact but warrants proactive mitigation. The vulnerability is particularly concerning for organizations relying on this client management system for sensitive customer data, as successful exploitation could compromise administrative control and data integrity.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats