Skip to main content
CVE-2025-7180VulnerabilityPublished

CVE-2025-7180: code-projects Staff Audit System · SQL Injection

Affects code-projects Staff Audit SystemSource 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 47% 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 8 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 Staff Audit SystemAffected
  • =1.0
Fixed in–

AI-suggested

Immediate mitigation steps include implementing input validation and parameterized queries or prepared statements to prevent SQL injection in the /login.php 'User' parameter. Organizations should conduct a thorough code review of the Staff Audit System to identify and remediate similar injection points. If vendor patches become available, prompt application is essential. In the absence of patches, deploying web application firewalls (WAFs) with custom rules to detect and block SQL injection payloads targeting the vulnerable parameter can reduce risk. Network segmentation and strict access controls around the Staff Audit System can limit exposure. Regular monitoring of logs for suspicious SQL queries or login attempts should be established to detect exploitation attempts early. Finally, organizations should consider migrating to updated or alternative audit systems with secure coding practices if remediation is not feasible.

Description

A vulnerability, which was classified as critical, has been found in code-projects Staff Audit System 1.0. This issue affects some unknown processing of the file /login.php. The manipulation of the argument User 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…