CVE-2025-51092: SQL Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 22 Aug 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 26 Oct 2026.
What to do
AI-suggested
To mitigate this vulnerability, organizations should immediately audit their use of the LogIn-SignUp project and identify any instances of the vulnerable DataBase.php implementation. The primary remediation is to refactor the logIn() and signUp() functions to use parameterized prepared statements for all SQL queries, ensuring that user inputs and table names are never directly concatenated into SQL commands. Since table names cannot be parameterized in prepared statements, implement strict whitelisting of allowed table names and validate them against this list before query construction. Additionally, enhance or replace the prepareData() function to include robust input validation and sanitization. Conduct thorough code reviews and penetration testing focused on SQL injection vectors. If patch updates become available from the original developer, apply them promptly. As an interim measure, consider deploying Web Application Firewalls (WAFs) with SQL injection detection rules tailored to this vulnerability’s patterns. Finally, monitor logs for suspicious SQL errors or anomalous query patterns indicative of exploitation attempts.
Description
The LogIn-SignUp project by VishnuSivadasVS is vulnerable to SQL Injection due to unsafe construction of SQL queries in DataBase.php. The functions logIn() and signUp() build queries by directly concatenating user input and unvalidated table names without using prepared statements. While a prepareData() function exists, it is insufficient to prevent SQL injection and does not sanitize the table name.