CVE Alert: CVE-2025-12243 – code-projects – Client Details System

CVE-2025-12243

MEDIUMNo exploitation knownPoC observed

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.

CVSS v3.1 (6.3)
Vendor
code-projects
Product
Client Details System
Versions
1.0
CWE
CWE-89, SQL Injection
Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Published
2025-10-27T07:02:16.794Z
Updated
2025-10-27T18:31:08.218Z

AI Summary Analysis

Risk verdict

Publicly exploitable SQL injection via a GET parameter handler; treat as priority 1 due to known public PoC and active exploitation risk.

Why this matters

Remote attackers can read or modify sensitive data without authentication, potentially exfiltrating or corrupting records. The presence of a publicly available exploit increases the likelihood of automated or opportunistic attacks targeting exposed web applications.

Most likely attack path

Remote, network-accessible injection with low attack complexity and no user interaction. An attacker supplies crafted ID values to trigger SQL injection, potentially bypassing strict input handling despite low privileges. Lateral movement is plausible only if the compromised component has DB privileges or access to other services.

Who is most exposed

Web-facing deployments that directly reflect or parameterise user-supplied IDs in SQL queries are at highest risk; common in small to mid-size servers running legacy GET parameter handlers with minimal input validation.

Detection ideas

  • Unusual or malformed SQL syntax observed in web/app logs related to ID parameter usage.
  • Database error messages or abnormal query errors aligned with crafted IDs.
  • Elevated query durations or abnormal spikes in authentication/DB activity after specific ID values.
  • IDS/WAF alerts for suspicious parameter patterns or SQL syntax in GET requests.
  • PoC exploit patterns or known signatures in historical access records.

Mitigation and prioritisation

  • Apply an urgent patch or mitigation to neutralise the injection (parameterised queries, prepared statements).
  • Implement input validation/sanitisation for the ID parameter; restrict to expected formats.
  • Enforce least-privilege DB accounts and disable unnecessary DB access from the web tier.
  • Add or strengthen WAF/+rules to block common SQL injection payloads.
  • Change-management: treat as priority 1; schedule a patch window and verify fixes in staging before production.

Support Our Work

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.

AI APIs OSINT driven New features