CVE-2025-14961
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 · uneditedA vulnerability was detected in code-projects Simple Blood Donor Management System 1.0. The affected element is an unknown function of the file /editedcampaign.php. The manipulation of the argument campaignname results in sql injection. The attack can be executed remotely. The exploit is now public and may be used.
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 confidenceA SQL injection vulnerability exists in the /editedcampaign.php file of Simple Blood Donor Management System 1.0. The campaignname parameter is not properly sanitized, allowing remote attackers to inject arbitrary SQL commands. This critical (CVSS 9.8) flaw can be exploited remotely without authentication.
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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the installed application is Simple Blood Donor Management System 1.0Locate and inspect any version identifier files (such as readme.txt, version.php, or about pages) in the web application root directory. Alternatively, check the page source or administrative interface for version information.Affected if The application is identified as Simple Blood Donor Management System version 1.0 from Fabian.
-
Locate the editedcampaign.php fileSearch the web application directory structure for the file editedcampaign.php. This is typically found in the root or admin directory of the Simple Blood Donor Management System installation.Affected if The file editedcampaign.php exists in the application directory.
-
Inspect the campaignname parameter handling in editedcampaign.phpOpen editedcampaign.php and examine how the campaignname POST parameter is processed. Search for SQL query construction that uses this parameter directly without sanitization or parameterized queries.Affected if The code shows direct insertion of the campaignname parameter into an SQL query string without using prepared statements or parameter binding.
-
Check for SQL query preparation patternsSearch the editedcampaign.php file for patterns such as 'prepare()', 'bindParam()', 'bindValue()', or '$stmt->' which indicate the use of prepared statements. Also check for input sanitization functions like mysqli_real_escape_string or htmlspecialchars being applied before the SQL query.Affected if No prepared statement methods or input sanitization functions are found before the SQL query executes with the campaignname value.
The environment is affected if Simple Blood Donor Management System version 1.0 is installed, the editedcampaign.php file exists, and the campaignname parameter is used in SQL queries without parameterized statements or proper input sanitization.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace dynamic SQL queries with parameterized queries or prepared statements for the campaignname parameter in editedcampaign.php. Audit other files in the application for similar SQL injection vulnerabilities.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14961 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-14961 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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