CVE-2025-4924
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, was found in SourceCodester Client Database Management System 1.0. Affected is an unknown function of the file /user_void_transaction.php. The manipulation of the argument order_id leads to sql injection. It is possible to launch the attack 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 in the /user_void_transaction.php file. The order_id parameter is not properly sanitized before being used in SQL queries, allowing attackers to inject arbitrary SQL commands. This can lead to unauthorized database access, data exfiltration, or potential system compromise.
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.
-
Identify the installed applicationLocate the SourceCodester or Lerouxyxchire Client Database Management System installation directory on the serverAffected if The application is present on the system
-
Verify the application versionCheck the version number of the installed Client Database Management System, typically found in a version file, README, or application metadataAffected if The installed version is 1.0
-
Locate the vulnerable PHP fileSearch for the file user_void_transaction.php within the application web root directoryAffected if The file user_void_transaction.php exists in the application
-
Inspect the order_id parameter handlingReview the source code of user_void_transaction.php and locate the database query that uses the order_id parameter. Verify whether the parameter is used directly in SQL queries without prepared statements, parameterized queries, or input sanitizationAffected if The order_id parameter is used in SQL queries without sanitization or prepared statements
-
Monitor for suspicious database activityReview database query logs or web server access logs for unusual or malicious SQL syntax in requests to user_void_transaction.php, particularly in the order_id parameterAffected if Evidence of SQL injection attempts or unauthorized queries targeting the order_id parameter exists
The environment is affected if the Client Database Management System version 1.0 is installed and the user_void_transaction.php file contains unsanitized order_id parameter usage in SQL queries.
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 dataImplement prepared statements/parameterized queries for all database operations, particularly for the order_id parameter in user_void_transaction.php. Conduct a comprehensive code review to identify and remediate similar SQL injection vulnerabilities throughout the application.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4924 — 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-4924 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