dbcve.org
Small CrmApplication · Phpgurukul

CVE-2025-10664

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-18
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 vulnerability was determined in PHPGurukul Small CRM 4.0. This impacts an unknown function of the file /create-ticket.php. Executing manipulation of the argument subject can lead to sql injection. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized.

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 allows remote attackers to inject malicious SQL code through the 'subject' parameter in /create-ticket.php. The lack of proper input sanitization or parameterized queries enables attackers to manipulate database queries.

MitigationReplace dynamic SQL queries with prepared statements (parameterized queries) for the 'subject' parameter in create-ticket.php, implement proper input validation, and apply vendor patches if available.

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 version
    Locate the version identifier in the application source code, typically in version files, readme files, or embedded constants
    Affected if The installed version is PHPGurukul Small CRM 4.0
  2. Verify create-ticket.php exists
    Check for the presence of the file /create-ticket.php in the application's web-accessible directory
    Affected if The file create-ticket.php exists and is accessible via the web server
  3. Inspect subject parameter handling
    Open create-ticket.php and locate code that processes the 'subject' parameter from POST or GET requests, then check if it is concatenated directly into SQL query strings
    Affected if The 'subject' parameter is used in SQL queries without prepared statements, parameter binding, or proper escaping
  4. Confirm database is in use
    Verify that the application is configured with a functional database connection and is actively using it
    Affected if The application uses a database that can process SQL queries

A user is affected if running PHPGurukul Small CRM version 4.0 with the create-ticket.php file accessible and the 'subject' parameter handled in SQL queries without parameterized 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with prepared statements (parameterized queries) for the 'subject' parameter in create-ticket.php, implement proper input validation, and apply vendor patches if available.

Recommended fix Moderate confidence

Latest patched release from PHPGurukul (contact vendor for version number)

  1. 1. Contact PHPGurukul directly to request the latest patched version of Small CRM
  2. 2. If a patched version is available, download it from the official source (phpgurukul.com) only
  3. 3. Before deploying, backup your current database and application files
  4. 4. Test the patched version in a staging environment to verify the SQL injection is resolved
  5. 5. Deploy the patched version to production
  6. 6. Verify the fix by testing the /create-ticket.php endpoint with the subject parameter - ensure parameterized queries are now used

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Small Crm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Check whether your project pulls in CVE-2025-10664 — 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-10664 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