CVE-2025-10114VulnerabilityPublished 9 Sep 2025

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

Affects PHPGurukul Small CRMSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 06:26 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 35% 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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
PHPGurukul Small CRM	Affected =4.0	Fixed in–

AI-suggested

1. Immediate mitigation should include restricting external access to the /profile.php endpoint via network controls such as firewalls or web application firewalls (WAFs) configured to detect and block SQL injection patterns targeting the 'Name' parameter. 2. Implement input validation and parameterized queries or prepared statements in the application code to eliminate SQL injection vectors; if source code modification is not feasible immediately, consider deploying virtual patching through WAF rules. 3. Conduct a thorough audit of all CRM inputs to identify and remediate similar injection vulnerabilities. 4. Monitor logs for suspicious query patterns or anomalous access attempts targeting the vulnerable parameter. 5. Segregate the CRM system within a secure network zone with limited access to sensitive backend databases. 6. Engage with the vendor or community to obtain or develop official patches and plan for timely updates. 7. Educate staff on the risks of SQL injection and ensure secure coding practices are followed in future development.

Description

A 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.

Impact

For European organizations using PHPGurukul Small CRM 4.0, this vulnerability poses a risk of unauthorized access to sensitive customer relationship management data. Exploitation could lead to leakage of personal or business-critical information, data integrity issues, and potential compliance violations under regulations such as GDPR. Although the severity is medium, the ease of remote exploitation without authentication increases the threat level, especially for organizations with externally accessible CRM instances. The impact is more pronounced for sectors handling sensitive data, including finance, healthcare, and government agencies. Additionally, compromised CRM data could be leveraged for further attacks such as phishing or social engineering. The absence of patches necessitates immediate mitigation to prevent exploitation, particularly in environments where the CRM is internet-facing or insufficiently segmented.

Summary

CVE-2025-10114 is a SQL Injection vulnerability identified in PHPGurukul Small CRM version 4.0, specifically within the /profile.php file. The vulnerability arises from improper sanitization or validation of the 'Name' parameter, which allows an attacker to manipulate SQL queries executed by the application. This flaw enables remote attackers to inject malicious SQL code without requiring authentication or user interaction, potentially leading to unauthorized data access or modification. The vulnerability has a CVSS 4.0 base score of 6.9, indicating a medium severity level. The attack vector is network-based (AV:N), with low attack complexity (AC:L), no privileges required (PR:N), and no user interaction needed (UI:N). The impact on confidentiality, integrity, and availability is low to limited, suggesting that while exploitation can lead to some data exposure or alteration, it may not result in full system compromise or denial of service. No known exploits are currently observed in the wild, and no patches have been officially released at the time of publication. The vulnerability is publicly disclosed, and exploit code is available, increasing the risk of exploitation if systems remain unpatched or unmitigated.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Sep 2025, 01:01 UTC

Technical details

References

Community reviews

Related threats