Skip to main content
CVE-2025-6884VulnerabilityPublished

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

Affects code-projects Staff Audit SystemSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jun 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

Since no official patches are currently available, European organizations should implement immediate compensating controls. These include: 1) Applying Web Application Firewalls (WAFs) with custom rules to detect and block SQL Injection patterns targeting the 'Search' parameter in /search_index.php. 2) Conducting thorough input validation and sanitization at the application layer, if source code access is possible, to neutralize malicious input. 3) Restricting database user permissions to the minimum necessary, preventing the exploited account from performing destructive operations. 4) Monitoring database logs and application logs for suspicious query patterns or anomalies indicative of injection attempts. 5) Isolating the Staff Audit System within segmented network zones to limit lateral movement in case of compromise. 6) Planning for an upgrade or replacement of the vulnerable software version once a vendor patch is released. 7) Conducting regular security assessments and penetration testing focused on injection vulnerabilities. These targeted measures go beyond generic advice by focusing on immediate risk reduction through network and application-layer controls, compensating for the lack of vendor patches.

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 /search_index.php. The manipulation of the argument Search 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…