CVE-2025-12243VulnerabilityPublished 27 Oct 2025

CVE-2025-12243: code-projects Client Details System · SQL Injection

Affects code-projects Client Details SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 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 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to 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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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

1. Immediately review and update the clientdetails/welcome.php code to implement parameterized queries or prepared statements for all database interactions involving user input, especially the 'ID' parameter. 2. Apply strict input validation and sanitization on all GET parameters to reject or neutralize malicious payloads. 3. Restrict database user permissions to the minimum necessary, preventing unauthorized data modification or deletion. 4. Monitor database logs and application logs for unusual query patterns or repeated failed attempts indicative of SQL injection attacks. 5. If patches become available from the vendor, prioritize their deployment in all affected environments. 6. Employ Web Application Firewalls (WAFs) with SQL injection detection rules tailored to this vulnerability as an interim protective measure. 7. Conduct security awareness training for developers to prevent similar vulnerabilities in future code. 8. Regularly audit and test the application using automated vulnerability scanners and manual penetration testing focused on injection flaws. 9. Segment networks to limit the impact of a compromised system and prevent lateral movement. 10. Maintain up-to-date backups to enable recovery in case of data corruption or deletion.

Description

A vulnerability was found in code-projects Client Details System 1.0. Affected by this issue is some unknown functionality of the file clientdetails/welcome.php of the component GET Parameter Handler. Performing manipulation of the argument ID results in sql injection. The attack may be initiated remotely. The exploit has been made public and could be used.

Impact

For European organizations, exploitation of this SQL injection vulnerability could lead to unauthorized access to sensitive client data, potentially violating GDPR and other data protection regulations. Data breaches could result in financial penalties, reputational damage, and operational disruptions. The integrity of client records could be compromised, affecting business processes and decision-making. Availability impacts could arise if attackers execute destructive SQL commands, leading to service downtime. Sectors such as finance, healthcare, and legal services that rely on client management systems are particularly vulnerable. The public availability of exploit code increases the likelihood of automated attacks targeting unpatched systems. Organizations with limited security resources or lacking robust input validation controls are at higher risk. The vulnerability also poses a risk of lateral movement within networks if attackers leverage compromised credentials or data. Overall, the threat could undermine trust in client management operations and expose organizations to regulatory scrutiny.

Summary

CVE-2025-12243 identifies a SQL injection vulnerability in the code-projects Client Details System version 1.0, specifically within the clientdetails/welcome.php file's GET parameter handler. The vulnerability arises from improper sanitization of the 'ID' parameter, allowing an attacker to inject arbitrary SQL commands remotely without requiring authentication or user interaction. The attack vector is network-based with low complexity, meaning an attacker can exploit it with minimal effort. The vulnerability impacts the confidentiality, integrity, and availability of the underlying database by enabling unauthorized data retrieval, modification, or deletion. Although no patches have been officially released, the public disclosure of exploit code increases the urgency for mitigation. The vulnerability does not involve scope changes or privilege escalation but can compromise sensitive client data managed by the system. The CVSS 4.0 vector indicates low complexity (AC:L), no privileges required (PR:L), no user interaction (UI:N), and partial impacts on confidentiality, integrity, and availability (L). This vulnerability is typical of classic SQL injection flaws caused by insufficient input validation and lack of parameterized queries. Organizations using this software should conduct immediate code reviews, implement input sanitization, and monitor for suspicious database queries to prevent exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 08:30 UTC

Technical details

References

Community reviews

Related threats