VulnerabilityPublished 15 Jan 2026

CVE-2025-70893: PHPGurukul Cyber Cafe Management System · SQL Injection

Source CVE Database V5

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

8.8High

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:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Jan 2026
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 26 Oct 2026.

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 or the CVSS exploit maturity 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

AI-suggested

Immediately audit and restrict access to the adminprofile.php endpoint to trusted administrators only, enforcing strong authentication mechanisms such as multi-factor authentication (MFA).
Implement strict input validation and sanitization for all user-supplied inputs, especially the 'adminname' parameter, using allowlists and rejecting suspicious characters.
Refactor the application code to use parameterized queries or prepared statements to prevent SQL injection attacks.
Monitor logs for unusual timing patterns or repeated failed attempts that may indicate exploitation attempts of time-based blind SQL injection.
Conduct regular security assessments and penetration testing focusing on injection flaws in the application.
Develop and deploy patches as soon as they become available from the vendor or community.
Educate administrators and users about credential security to reduce the risk of compromised accounts.
Segment the network to limit the impact of a potential breach and isolate critical databases from direct web access.
Employ Web Application Firewalls (WAFs) with rules designed to detect and block SQL injection attempts, including time-based blind techniques.
Maintain up-to-date backups and have an incident response plan ready to quickly recover from any successful exploitation.

Description

CVE-2025-70893 is a high-severity time-based blind SQL Injection vulnerability in the PHPGurukul Cyber Cafe Management System v1.0, specifically in the adminprofile.php endpoint. It arises from improper sanitization of the adminname parameter, allowing authenticated attackers to inject arbitrary SQL commands. Exploitation requires authentication but no user interaction, and can lead to full compromise of confidentiality, integrity, and availability of the backend database. No public exploits are known yet, but the vulnerability's high CVSS score (8.8) indicates significant risk. European organizations using this system, especially cyber cafes or similar service providers, could face data breaches or service disruptions. Mitigation involves applying patches once available, employing strict input validation, and using parameterized queries. Countries with higher usage of PHPGurukul or similar cyber cafe management systems, and those with significant cyber cafe presence, are more likely to be affected.

Impact

For European organizations, the exploitation of CVE-2025-70893 could lead to severe consequences including unauthorized disclosure of sensitive data, corruption or deletion of critical records, and disruption of cyber cafe management operations. Given that the vulnerability affects a cyber cafe management system, attackers could gain access to administrative functions, potentially compromising user data, payment information, and operational controls. This could result in financial losses, reputational damage, and regulatory penalties under GDPR due to data breaches. The requirement for authentication limits the attack surface but does not eliminate risk, especially in environments with weak credential management or insider threats. The high impact on confidentiality, integrity, and availability means that exploited systems could be fully compromised, affecting business continuity. European cyber cafes and similar service providers relying on PHPGurukul or comparable systems are particularly vulnerable, and the threat could extend to any connected networks or integrated services. The absence of known exploits in the wild currently provides a window for proactive defense, but the potential for rapid weaponization remains high.

Summary

CVE-2025-70893 identifies a time-based blind SQL Injection vulnerability in the PHPGurukul Cyber Cafe Management System version 1.0, specifically within the adminprofile.php endpoint. The vulnerability stems from the failure to properly sanitize the 'adminname' parameter, which is user-supplied input. Authenticated attackers can exploit this flaw by injecting arbitrary SQL expressions, leveraging the time-based blind SQL injection technique to infer data from the backend database without direct output. This type of injection allows attackers to extract sensitive information, modify or delete data, and potentially escalate privileges within the application. The vulnerability requires the attacker to be authenticated but does not require additional user interaction, increasing the risk in environments where credentials may be compromised or weak. The CVSS score of 8.8 (high severity) reflects the vulnerability's network attack vector, low attack complexity, requirement for privileges, and its impact on confidentiality, integrity, and availability. Although no public exploits are currently known, the vulnerability's characteristics make it a significant threat to affected systems. The lack of available patches at the time of publication necessitates immediate mitigation efforts by administrators. This vulnerability is classified under CWE-89, which covers SQL Injection flaws. The time-based blind nature means attackers can use timing delays to infer database contents, making detection and prevention critical to avoid data breaches or system compromise.

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 22 Jan 2026, 21:31 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats