CVE-2025-10114
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 PHPGurukul Small CRM 4.0. Affected by this issue is some unknown functionality of the file /profile.php. The manipulation of the argument Name results in sql injection. The attack can be launched remotely. The exploit has been made public and could 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 confidenceSQL injection vulnerability in PHPGurukul Small CRM 4.0's /profile.php allows remote attackers to inject malicious SQL queries via the 'Name' parameter. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially exfiltrating, modifying, or deleting sensitive data.
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= 4.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 PHPGurukul Small CRM versionLocate the version file or check the source code for a version identifier. Common locations include a version.php file, footer comments, or an admin/about page displaying the software version.Affected if The installed version is exactly 4.0 (no patch applied)
-
Verify profile.php existsCheck the web server document root for the file /profile.php. This is the file containing the vulnerable 'Name' parameter handling.Affected if profile.php exists and is accessible via the web server
-
Inspect profile.php for SQL injection vulnerabilityOpen profile.php in a text editor or use 'grep' to search for the 'Name' parameter handling. Look for SQL queries that directly incorporate $_POST or $_GET['Name'] without using prepared statements or parameter binding.Affected if The code contains SQL queries that concatenate the 'Name' parameter directly without sanitization or prepared statements
-
Check for input sanitization functionsSearch the profile.php file for sanitization functions such as mysqli_real_escape_string, htmlspecialchars, or other input validation methods applied to the Name parameter before database operations.Affected if No sanitization functions are found for the Name parameter in SQL queries
-
Review web server access logs for exploitation attemptsExamine web server access logs (Apache access.log, Nginx access.log) for requests to /profile.php containing SQL injection payloads in the Name parameter, such as quotes, UNION SELECT, or boolean-based injection patterns.Affected if Log entries show SQL injection attempts targeting the Name parameter in profile.php
The environment is affected if PHPGurukul Small CRM version 4.0 is installed, profile.php is accessible, and the code contains unsanitized SQL queries using the Name 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 dataImplement prepared statements/parameterized queries for all user-supplied input in profile.php, particularly the Name parameter. Validate and sanitize all user inputs before database operations.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10114 — 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-10114 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