Skip to main content
CVE-2025-7514VulnerabilityPublished Updated

CVE-2025-7514: code-projects Modern Bag · SQL Injection

Affects code-projects Modern BagSource 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 13 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 Modern BagAffected
  • =1.0
Fixed in–

AI-suggested

1. Immediate application of any available patches or updates from the vendor once released is critical. Since no patches are currently available, organizations should implement temporary mitigations. 2. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious SQL injection patterns targeting the 'idStatus' parameter in /admin/contact-list.php. 3. Restrict access to the /admin directory by IP whitelisting or VPN-only access to reduce exposure to unauthenticated attackers. 4. Conduct thorough input validation and sanitization on all parameters, especially 'idStatus', to ensure only expected values are processed. 5. Monitor application logs for unusual query patterns or repeated access attempts to the vulnerable endpoint. 6. Consider deploying database activity monitoring to detect anomalous SQL queries indicative of injection attempts. 7. Plan for an urgent update cycle once the vendor releases a patch, and test the patch in a controlled environment before deployment. 8. Educate development and security teams about secure coding practices to prevent similar vulnerabilities in future releases.

Description

A vulnerability was found in code-projects Modern Bag 1.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file /admin/contact-list.php. The manipulation of the argument idStatus leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…