dbcve.org
Client Details SystemApplication · Fabian

CVE-2025-6446

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability, which was classified as critical, has been found in code-projects Client Details System 1.0. This issue affects some unknown processing of the file /clientdetails/admin/index.php. The manipulation of the argument Username leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in the Client Details System 1.0 admin login page (/clientdetails/admin/index.php) allows remote attackers to inject malicious SQL queries via the Username parameter. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially extracting sensitive data, bypassing authentication, or compromising the entire database.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements in the affected PHP file. Additionally, implement input validation and output encoding. Apply the latest vendor patch if available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Client Details SystemApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Fabian Client Details System is installed
    Search your web server directories for the 'clientdetails' folder or the file '/clientdetails/admin/index.php'. Common locations include web root directories like /var/www/html or C:\inetpub\wwwroot.
    Affected if The /clientdetails/admin/index.php file exists on the server
  2. Verify the installed version
    Check any version information in the application source code, such as a README file, a config file, or metadata within the PHP files. Compare against version 1.0.
    Affected if The installed version is Fabian Client Details System 1.0
  3. Confirm the admin login page is accessible
    Attempt to access the URL path /clientdetails/admin/index.php via HTTP or HTTPS from your web server. A 200 response indicates the page exists and is reachable.
    Affected if The admin login page responds with HTTP 200 and displays a login form
  4. Test the Username parameter for SQL injection
    Submit a login request with a single quote (') in the Username field, such as admin'. Observe whether the application returns a SQL error message, behaves unexpectedly, or the response differs significantly from a normal failed login.
    Affected if The application returns a database SQL error message or exhibits abnormal behavior indicating SQL injection vulnerability
  5. Check for SQL injection indicators in application logs
    Review web server error logs (such as Apache error.log or PHP error logs) for SQL syntax errors or warnings related to the login query when the Username parameter is processed.
    Affected if SQL-related error messages appear in logs referencing queries from the login page

You are affected if Fabian Client Details System version 1.0 is installed, the admin login page at /clientdetails/admin/index.php is accessible, and the Username parameter exhibits SQL injection behavior.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries or prepared statements in the affected PHP file. Additionally, implement input validation and output encoding. Apply the latest vendor patch if available.

Recommended fix Low confidence
  1. Deploy a Web Application Firewall (WAF) rule to detect and block SQL injection attempts targeting the /clientdetails/admin/index.php endpoint, specifically the Username parameter.
  2. Restrict access to the admin page /clientdetails/admin/index.php by IP whitelisting or basic authentication to limit exposure to remote attackers.
  3. Implement strict input validation and sanitization for the Username parameter (e.g., use whitelisting of allowed characters, length limits).
  4. If the admin interface is not required in production, disable or remove the /clientdetails/admin/index.php file.
  5. Monitor logs for SQL injection attack patterns and update WAF rules as needed.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Client Details System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6446 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6446 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data