Skip to main content
CVE-2025-7556VulnerabilityPublished

CVE-2025-7556: code-projects Voting System · SQL Injection

Affects code-projects Voting 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 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 Voting SystemAffected
  • =1.0
Fixed in–

AI-suggested

Given the absence of an official patch, European organizations should implement immediate compensating controls. These include: 1) Restricting access to the /admin/voters_edit.php endpoint through network segmentation and firewall rules to trusted IP addresses only. 2) Employing Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the 'ID' parameter. 3) Conducting thorough input validation and sanitization on all user-supplied data, especially parameters used in SQL queries, ideally using parameterized queries or prepared statements if source code modification is possible. 4) Monitoring logs for unusual database query patterns or repeated access attempts to the vulnerable endpoint. 5) Planning for an upgrade or replacement of the vulnerable Voting System version once a vendor patch or secure alternative is available. 6) Educating administrators about the vulnerability and ensuring strict credential management to prevent privilege escalation.

Description

A vulnerability, which was classified as critical, was found in code-projects Voting System 1.0. Affected is an unknown function of the file /admin/voters_edit.php. The manipulation of the argument ID leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…