Skip to main content
VulnerabilityPublished Updated

CVE-2025-69564: Code Injection

Source CVE Database V5

0

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.4% chance of exploitation in 30 days – higher than 40% 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

  1. Immediately implement input validation and sanitization on all user-supplied data fields in /ExAddNewUser.php, ensuring that special characters are properly escaped or rejected.
  2. Refactor the application code to use parameterized queries or prepared statements to prevent SQL Injection attacks.
  3. Restrict database user permissions to the minimum necessary, avoiding use of high-privilege accounts for application database connections.
  4. Monitor database logs and application logs for unusual or suspicious SQL queries indicative of injection attempts.
  5. Deploy Web Application Firewalls (WAFs) with rules targeting SQL Injection patterns to provide an additional layer of defense.
  6. Conduct thorough code reviews and security testing (including automated scanning and manual penetration testing) of the affected application components.
  7. Isolate the affected system within the network to limit potential lateral movement in case of compromise.
  8. Engage with the software vendor or development team to obtain and apply official patches or updates as soon as they become available.
  9. Educate development and operations teams about secure coding practices to prevent similar vulnerabilities in future releases.
  10. Prepare and test incident response plans to quickly address any exploitation attempts.

Description

CVE-2025-69564 is a critical SQL Injection vulnerability affecting the code-projects Mobile Shop Management System 1.0. The flaw exists in the /ExAddNewUser.php endpoint, where multiple parameters including Name, Address, email, UserName, Password, confirm_password, Role, Branch, and Activate are vulnerable to injection. This vulnerability allows an unauthenticated attacker to execute arbitrary SQL commands remotely without user interaction, potentially leading to full compromise of the backend database. The CVSS score is 9.8, indicating high impact on confidentiality, integrity, and availability. Although no known exploits are currently in the wild, the ease of exploitation and critical impact make this a severe threat. European organizations using this system, especially retail and shop management businesses, face risks of data breaches, data manipulation, and service disruption. Immediate mitigation involves input validation, parameterized queries, and applying patches once available.

References

Community reviews

Loading reviews…