Skip to main content
VulnerabilityPublished

CVE-2026-7731: code-projects BloodBank Managing System · SQL Injection

Affects code-projects BloodBank Managing SystemSource CVE Database V5

0
Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% 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 4 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
code-projectsBloodBank Managing SystemAffected
  • =1.0
Fixed in–

AI-suggested

In the absence of an official fix, users should consider implementing input validation or parameterized queries on the G_STATE_ID parameter as a temporary mitigation. Monitor vendor channels for updates and apply official patches once available.

Description

A security vulnerability has been detected in code-projects BloodBank Managing System 1.0. The affected element is an unknown function of the file get_state.php. The manipulation of the argument G_STATE_ID leads to sql injection. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used.

References

Community reviews

Loading reviews…