Skip to main content
CVE-2025-7409VulnerabilityPublished

CVE-2025-7409: 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.4% chance of exploitation in 30 days – higher than 41% 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 10 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

1. Immediate code review and sanitization of all inputs, especially the 'email' parameter in /LoginAsAdmin.php, using parameterized queries or prepared statements to prevent SQL Injection. 2. Implement Web Application Firewalls (WAFs) with rules specifically designed to detect and block SQL Injection attempts targeting this endpoint. 3. Conduct thorough penetration testing and code audits on the Mobile Shop application to identify and remediate any other injection points. 4. Restrict database user privileges to the minimum necessary for application functionality to limit the impact of a successful injection. 5. Monitor application logs and network traffic for unusual patterns indicative of exploitation attempts. 6. If possible, isolate the vulnerable application behind VPN or internal networks until a patch or fix is available. 7. Engage with the vendor or community to obtain or develop patches and apply them promptly once available. 8. Educate development teams on secure coding practices to prevent similar vulnerabilities in future releases.

Description

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

References

Community reviews

Loading reviews…