VulnerabilityPublished 27 Jan 2026Updated 28 Jan 2026

CVE-2025-69563: CVE-2025-69563 is a critical SQL Injection

Source CVE Database V5

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

9.8Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 44% 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:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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 27 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

Since no official patches are currently available, immediate mitigation should focus on implementing strong input validation and sanitization on the Password parameter in /ExLogin.php. Employing parameterized queries or prepared statements will prevent SQL injection attacks by separating code from data. Organizations should conduct thorough code reviews and penetration testing to identify and remediate similar injection points. Network-level protections such as Web Application Firewalls (WAFs) can be configured to detect and block SQL injection attempts targeting this endpoint. Monitoring and logging of database queries and login attempts should be enhanced to detect suspicious activities early. If possible, restrict access to the vulnerable endpoint via IP whitelisting or VPNs until a patch is released. Organizations should also prepare incident response plans specific to SQL injection attacks and ensure backups are up to date to enable recovery from potential data corruption or deletion.

Description

CVE-2025-69563 is a critical SQL Injection vulnerability in code-projects Mobile Shop Management System 1.0, specifically in the /ExLogin.php script via the Password parameter. This vulnerability allows unauthenticated remote attackers to execute arbitrary SQL commands, potentially leading to full compromise of the backend database. The CVSS score of 9.8 reflects the high impact on confidentiality, integrity, and availability without requiring authentication or user interaction. Although no known exploits are currently reported in the wild, the ease of exploitation and severity make it a significant threat. European organizations using this system are at risk of data breaches, unauthorized access, and service disruption. Immediate mitigation involves applying patches or implementing input validation and parameterized queries. Countries with higher adoption of this software or with strategic retail and mobile commerce sectors are more likely to be affected.

Impact

For European organizations, exploitation of this vulnerability could lead to severe data breaches involving sensitive customer and business information, undermining confidentiality. Integrity of transactional and inventory data could be compromised, leading to financial discrepancies and loss of trust. Availability of the Mobile Shop Management System could be disrupted, affecting business continuity and customer service. Retailers and mobile commerce operators using this system may face regulatory penalties under GDPR due to inadequate protection of personal data. The critical nature of the vulnerability means attackers could remotely execute arbitrary SQL commands without authentication, increasing the risk of widespread exploitation. This could also facilitate lateral movement within networks, potentially exposing other connected systems. The reputational damage and financial losses from such incidents could be substantial, especially for SMEs relying heavily on this software for daily operations.

Summary

CVE-2025-69563 identifies a critical SQL Injection vulnerability in the Mobile Shop Management System 1.0 developed by code-projects. The vulnerability exists in the /ExLogin.php endpoint, specifically through the Password parameter, which fails to properly sanitize user input before incorporating it into SQL queries. This flaw allows remote attackers to inject malicious SQL code without requiring authentication or user interaction, enabling them to manipulate the backend database. Potential consequences include unauthorized data disclosure, modification, deletion, or even full system compromise. The vulnerability is classified under CWE-89 (Improper Neutralization of Special Elements used in an SQL Command). The CVSS v3.1 base score of 9.8 indicates a critical severity with network attack vector, low attack complexity, no privileges required, no user interaction, and impacts on confidentiality, integrity, and availability. Although no patches or known exploits are currently documented, the vulnerability's nature and criticality necessitate urgent attention. The absence of affected version details suggests all instances of version 1.0 might be vulnerable. Organizations relying on this system for managing mobile shop operations face significant risks of data breaches and operational disruptions if exploited.

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 4 Feb 2026, 09:18 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats