CVE-2025-3175
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 was found in Project Worlds Online Lawyer Management System 1.0 and classified as critical. Affected by this issue is some unknown functionality of the file /save_user_edit_profile.php. The manipulation of the argument first_Name leads to sql injection. The attack may be launched 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's /save_user_edit_profile.php file. The 'first_Name' parameter is not properly sanitized before being used in database queries, allowing remote attackers to inject arbitrary SQL commands.
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 Online Lawyer Management System is installedSearch for the application in your web root directory. Look for folders containing 'lawyer' or check known web directories. Look for the presence of PHP files from this application.Affected if The application is found in the web directory and the version is 1.0
-
Verify the vulnerable PHP file existsLocate the file /save_user_edit_profile.php in the web application directory. This file is typically in the admin or user profile management area of the application.Affected if The file /save_user_edit_profile.php exists in the application structure
-
Check if user profile editing is accessibleDetermine if the profile editing functionality is enabled and accessible. This typically requires user authentication to access the endpoint that calls save_user_edit_profile.php.Affected if The profile editing feature is enabled and accessible to users or administrators
-
Confirm the application versionCheck the application version by reviewing any version.php file, README, or meta information in the application root. Yugesh Verma Online Lawyer Management System version 1.0 is affected.Affected if The installed version is exactly 1.0 (no other versions are listed as affected)
-
Inspect the vulnerable parameter handlingReview the save_user_edit_profile.php file code. Look for the 'first_Name' parameter usage in SQL queries without prepared statements or proper sanitization.Affected if The code shows direct use of the 'first_Name' parameter in SQL queries without parameterized statements or input sanitization
The environment is affected if Online Lawyer Management System version 1.0 is installed with the save_user_edit_profile.php file accessible and the first_Name parameter handled without prepared statements 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 dataReplace dynamic SQL queries with parameterized statements/prepared statements to neutralize the injection vector. Implement strict input validation as an additional defense layer.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3175 — 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-3175 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