dbcve.org
Blood Bank And Donation Management SystemApplication · Varunsardana004

CVE-2025-11481

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-08
Fix available
A fix is available. Upgrade to after 2021-03-18 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw has been found in varunsardana004 Blood-Bank-And-Donation-Management-System up to dc9e0393d826fbc85fad9755b5bc12cba1919df2. The impacted element is an unknown function of the file /donate_blood.php. Executing manipulation of the argument fullname can lead to sql injection. The attack may be performed from remote. The exploit has been published and may be used. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in the /donate_blood.php file of the Blood-Bank-And-Donation-Management-System allows remote attackers to manipulate the fullname parameter to inject arbitrary SQL commands, potentially exposing or manipulating the entire database.

MitigationImplement prepared statements/parameterized queries for all user inputs in donate_blood.php, specifically for the fullname parameter, and apply input validation/sanitization before database operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Blood Bank And Donation Management SystemApplication
Affected:<= 2021-03-18

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm application installation
    Locate the Blood Bank And Donation Management System in your web server directory. Check for files or directories containing 'blood-bank' or 'donate_blood.php'.
    Affected if The application is present on the server and accessible via web.
  2. Check application version
    Examine version information in the source code, README, or any version file. The affected version is dated 2021-03-18 or earlier. Look for date metadata in the codebase.
    Affected if The installed version has a date on or before 2021-03-18.
  3. Locate vulnerable file
    Search the web root for the file /donate_blood.php. If using a PHP code scanner, search for files containing the fullname parameter in POST/GET requests.
    Affected if The file donate_blood.php exists in the application directory.
  4. Inspect fullname parameter handling
    Open donate_blood.php and examine how the fullname POST/GET parameter is processed. Search for SQL queries that use fullname without prepared statements, parameter binding, or escaping functions like mysqli_real_escape_string.
    Affected if The fullname parameter is directly concatenated into an SQL query without parameterized queries or proper escaping.
  5. Verify database interaction exists
    Check if the donate_blood.php file contains SQL queries (SELECT, INSERT, UPDATE) that incorporate the fullname user input. Look for database connection code and query execution functions.
    Affected if The file contains SQL queries that incorporate the fullname parameter directly.

The environment is affected if the Blood Bank And Donation Management System is installed with a version dated 2021-03-18 or earlier AND the donate_blood.php file exists AND the fullname parameter is used in SQL queries without prepared statements or proper escaping.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 2021-03-18
Interim mitigation

Implement prepared statements/parameterized queries for all user inputs in donate_blood.php, specifically for the fullname parameter, and apply input validation/sanitization before database operations.

Fix this in Blood Bank And Donation Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11481 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11481 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data