VulnerabilityPublished 27 Jan 2026Updated 28 Jan 2026

CVE-2025-69562: code-projects Mobile Shop Management System · SQL Injection

Source CVE Database V5

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 12:55 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

Immediate code review and remediation: Developers should implement parameterized queries or prepared statements for all database interactions involving user input, especially the userid parameter in /insertmessage.php.
Input validation: Enforce strict input validation and sanitization on all user-supplied data to reject malicious payloads.
Web application firewall (WAF): Deploy and configure a WAF with rules to detect and block SQL Injection attempts targeting the vulnerable endpoint.
Network segmentation: Isolate the vulnerable application and its database from critical internal networks to limit lateral movement in case of compromise.
Monitoring and logging: Enable detailed logging of database queries and web requests to detect suspicious activity and facilitate incident response.
Access controls: Restrict database user privileges to the minimum necessary to reduce the impact of a successful injection.
Patch management: Monitor for official patches or updates from the vendor and apply them promptly once available.
Incident response planning: Prepare for potential exploitation scenarios with defined response procedures to minimize damage.
Vendor engagement: Contact the software vendor for guidance, timelines for patches, and possible workarounds.
Alternative solutions: Evaluate replacing the vulnerable system with more secure alternatives if remediation is delayed.

Description

CVE-2025-69562 is a critical SQL Injection vulnerability found in code-projects Mobile Shop Management System 1.0, specifically in the /insertmessage.php script via the userid 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. Exploitation could result in data theft, data manipulation, or complete system takeover. No known exploits are currently reported in the wild, and no patches have been published yet. European organizations using this system, especially retailers and mobile shop operators, face significant risks. Mitigation should focus on immediate input validation, use of prepared statements, and network-level protections.

Impact

For European organizations, especially those operating retail or mobile shop management systems using this vulnerable software, the impact could be severe. Confidential customer data, including personal and transactional information, could be stolen, leading to privacy violations and regulatory penalties under GDPR. Integrity of business data could be compromised, resulting in fraudulent transactions, inventory manipulation, or financial losses. Availability could also be affected if attackers delete or corrupt critical data, disrupting business operations. The reputational damage from a breach could be significant, affecting customer trust and market position. Given the critical severity and ease of exploitation, attackers could rapidly weaponize this vulnerability to target multiple organizations. The lack of patches means organizations must rely on immediate mitigations to reduce risk. The threat is particularly relevant to European countries with a strong retail sector or where this software has market penetration, as well as those with stringent data protection regulations that increase the cost of breaches.

Summary

The vulnerability identified as CVE-2025-69562 affects the code-projects Mobile Shop Management System version 1.0. It is a classic SQL Injection (CWE-89) vulnerability located in the /insertmessage.php endpoint, specifically through the userid parameter. SQL Injection occurs when user-supplied input is improperly sanitized and directly concatenated into SQL queries, allowing attackers to manipulate the database queries executed by the application. In this case, the userid parameter is not properly validated or escaped, enabling an attacker to inject malicious SQL code remotely without any authentication or user interaction. The CVSS 3.1 base score of 9.8 indicates a critical severity, with attack vector being network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), unchanged scope (S:U), and high impacts on confidentiality (C:H), integrity (I:H), and availability (A:H). This means an attacker can fully compromise the backend database, potentially extracting sensitive customer data, modifying or deleting records, or even executing administrative commands if the database user has elevated privileges. Although no public exploits have been reported yet, the vulnerability’s nature and severity make it a prime target for attackers once exploit code becomes available. The lack of available patches or updates increases the urgency for organizations to implement interim mitigations. The vulnerability affects all deployments of the Mobile Shop Management System 1.0 that expose the vulnerable endpoint and do not have compensating controls in place.

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