Skip to main content
CVE-2025-7612VulnerabilityPublished

CVE-2025-7612: code-projects Mobile Shop · SQL Injection

Affects code-projects Mobile ShopSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Jul 2025

  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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
code-projects Mobile ShopAffected
  • =1.0
Fixed in–

AI-suggested

Immediate mitigation steps include: 1) Conducting an urgent inventory to identify any deployments of code-projects Mobile Shop version 1.0 within the organization. 2) Applying input validation and parameterized queries or prepared statements to the /login.php email parameter to prevent SQL injection. Since no official patches are available, organizations should implement temporary web application firewall (WAF) rules to detect and block malicious SQL injection payloads targeting the email parameter. 3) Restrict database user permissions to the minimum necessary to limit the impact of any injection attack. 4) Monitor logs for suspicious login attempts or unusual database errors indicative of exploitation attempts. 5) Engage with the vendor or community to obtain patches or updates as soon as they become available. 6) Consider isolating or decommissioning vulnerable instances until a fix is applied. 7) Educate development teams on secure coding practices to prevent similar vulnerabilities in future releases. These steps go beyond generic advice by focusing on immediate detection, containment, and compensating controls in the absence of a patch.

Description

A vulnerability was found in code-projects Mobile Shop 1.0. It has been declared as critical. This vulnerability affects unknown code of the file /login.php. The manipulation of the argument email leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…