CVE-2025-6160
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 · uneditedA vulnerability, which was classified as critical, has been found in SourceCodester Client Database Management System 1.0. This issue affects some unknown processing of the file /user_customer_create_order.php. The manipulation of the argument user_id 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 confidenceA critical SQL injection vulnerability exists in SourceCodester Client Database Management System 1.0. The user_id parameter in /user_customer_create_order.php is not properly sanitized, allowing remote attackers to inject arbitrary SQL commands. The exploit is publicly 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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify the application is installedLocate the SourceCodester Client Database Management System installation directory. Look for the file /user_customer_create_order.php within the web root.Affected if The file /user_customer_create_order.php exists in the web application directory and is accessible.
-
Confirm the product versionCheck the version of the installed SourceCodester Client Database Management System. This may be in a README file, a version config, or the application header/footer.Affected if The installed version is exactly 1.0.
-
Inspect the vulnerable file for the SQL injection flawOpen /user_customer_create_order.php and search for the user_id parameter. Look for SQL queries that directly incorporate the user_id without using prepared statements or parameter binding.Affected if The code contains SQL queries that concatenate or interpolate the user_id parameter directly into the query string without sanitization.
-
Check if the vulnerable endpoint is reachableAttempt to access /user_customer_create_order.php via HTTP to confirm it is an active route. Verify that the user_id parameter is accepted as input.Affected if The endpoint is accessible and accepts a user_id parameter without apparent input validation.
-
Review application logs for suspicious SQL activityExamine web server access logs and application logs for unusual SQL syntax in requests to /user_customer_create_order.php that may indicate exploitation attempts.Affected if Requests to the endpoint contain SQL injection payloads in the user_id parameter.
You are affected if SourceCodester Client Database Management System version 1.0 is installed and the file /user_customer_create_order.php contains direct SQL query concatenation with the user_id parameter.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataReplace dynamic SQL queries with parameterized queries/prepared statements for the user_id parameter, implement input validation, and apply the principle of least privilege to database accounts.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6160 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-6160 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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