CVE-2025-3172
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 Project Worlds Online Lawyer Management System 1.0. This issue affects some unknown processing of the file /lawyer_booking.php. The manipulation of the argument unblock_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 SQL injection vulnerability exists in the Online Lawyer Management System 1.0 in the /lawyer_booking.php file. The unblock_id parameter is not properly sanitized before being used in SQL queries, allowing attackers to inject malicious SQL commands. This can lead to unauthorized database access, data exfiltration, or potential remote code execution depending on database configuration.
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.
-
Confirm the application is installedLocate the Online Lawyer Management System by searching for files like 'lawyer_booking.php', 'index.php', or directories containing 'lawyer' in the web root path. Check for application-specific folders or known installation paths.Affected if The application is present on the system and the web server is serving it.
-
Verify the exact versionCheck the application version by examining version files, README files, or the source code for a version string. Common locations include a 'version' file, 'about' page, or header/footer comments in PHP files.Affected if The installed version is exactly 1.0.
-
Locate the vulnerable fileSearch for the file 'lawyer_booking.php' within the web application directory structure. This file handles booking operations and contains the vulnerable parameter.Affected if The file lawyer_booking.php exists in the application.
-
Identify unblock_id parameter usageOpen lawyer_booking.php and search for occurrences of 'unblock_id' in the code. Verify if this parameter is being used in SQL query construction without visible sanitization or prepared statements.Affected if The parameter 'unblock_id' is present and used in SQL queries without evident parameterized query implementation.
-
Test the parameter if accessibleIf the application is live and accessible, review HTTP request logs or attempt a safe test: send a request to lawyer_booking.php with a test value for unblock_id (such as '1') and observe the application's response behavior.Affected if The application accepts and processes the unblock_id parameter in HTTP requests.
You are affected if you have Online Lawyer Management System version 1.0 installed with the lawyer_booking.php file present and the unblock_id parameter being processed in SQL queries without prepared statements.
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 dataFix the SQL injection by implementing parameterized queries/prepared statements for all database operations using the unblock_id parameter. Apply input validation and ensure the database user follows least privilege principles.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3172 — 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-3172 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