Skip to main content
CVE-2025-10664VulnerabilityPublished

CVE-2025-10664: PHPGurukul Small CRM · SQL Injection

Affects PHPGurukul Small CRMSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
PHPGurukul Small CRMAffected
  • =4.0
Fixed in–

AI-suggested

1. Immediate application of patches or updates from PHPGurukul once available is the most effective mitigation. 2. Implement Web Application Firewall (WAF) rules to detect and block SQL injection patterns targeting the 'subject' parameter in /create-ticket.php. 3. Conduct thorough input validation and sanitization on all user-supplied data, especially the 'subject' field, using parameterized queries or prepared statements to prevent SQL injection. 4. Perform security audits and code reviews focusing on database interaction points within the CRM application. 5. Restrict database user permissions to the minimum necessary to limit the impact of any successful injection. 6. Monitor logs for unusual database queries or errors that may indicate attempted exploitation. 7. If immediate patching is not possible, consider isolating the CRM system from direct internet exposure or implementing VPN access controls to reduce attack surface. 8. Educate IT and security teams about this vulnerability and ensure incident response plans include steps for SQL injection incidents.

Description

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.

References

Community reviews

Loading reviews…