dbcve.org
Small CrmApplication · Phpgurukul

CVE-2025-11053

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A weakness has been identified in PHPGurukul Small CRM 4.0. This affects an unknown function of the file /forgot-password.php. Executing manipulation of the argument email can lead to sql injection. The attack can be launched remotely. The exploit has been made available to the public and could be exploited.

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 confidence

SQL injection vulnerability in PHPGurukul Small CRM 4.0's forgot-password.php allows remote attackers to inject malicious SQL queries via the unsanitized email parameter.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries for the email parameter and implement proper input validation.

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
Small CrmApplication
Affected:= 4.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm PHPGurukul Small CRM installation
    Locate the CRM installation directory by searching for 'small-crm' folder or index.php with CRM branding. Check web root for PHP files containing 'Small CRM' or 'PHPGurukul' text.
    Affected if The software is installed and accessible on the web server
  2. Identify the exact version
    Check version.php, README.txt, or any version file in the CRM root directory for version number. Also check footer text in login.php or other pages for version disclosure.
    Affected if Version is 4.0 specifically (exact match)
  3. Locate forgot-password.php
    Navigate to the /forgot-password.php file in the web application directory. This is the vulnerable file mentioned in the CVE.
    Affected if The file exists in the expected location
  4. Inspect email parameter handling in forgot-password.php
    Open forgot-password.php and examine the code that processes the 'email' parameter from POST/GET requests. Look for SQL queries that directly incorporate the email variable without prepared statements.
    Affected if The code uses direct string concatenation or string interpolation to build SQL queries with the email parameter (e.g., "SELECT * FROM users WHERE email = '$email'")
  5. Verify if prepared statements are NOT used
    Search the forgot-password.php file for 'prepare', 'bindParam', 'bindValue', or 'stmt' functions. Also check for PDO or mysqli prepared statement patterns.
    Affected if No prepared statements or parameter binding are found for the email parameter in SQL queries, meaning user input flows directly into the query
  6. Confirm database interaction exists with email input
    Check if the forgot-password.php actually queries the database using the email parameter for password reset functionality.
    Affected if The page performs database lookups using the email input without sanitization

A user is affected if they have PHPGurukul Small CRM version 4.0 installed with the forgot-password.php file containing direct SQL query construction using the email parameter without prepared statements.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with prepared statements/parameterized queries for the email parameter and implement proper input validation.

Fix this in Small Crm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11053 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11053 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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