CVE-2024-2517
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 has been found in MAGESH-K21 Online-College-Event-Hall-Reservation-System 1.0 and classified as critical. This vulnerability affects unknown code of the file book_history.php. The manipulation of the argument del_id leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-256954 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceSQL injection vulnerability in the book_history.php file of MAGESH-K21 Online-College-Event-Hall-Reservation-System 1.0. The del_id parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL code. A public exploit exists (VDB-256954).
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 installed product and versionLocate the web application files and identify if the application is MAGESH-K21 Online-College-Event-Hall-Reservation-System. Check for version indicators in source files, readme files, or admin panels.Affected if The application is installed and the version is 1.0 exactly
-
Locate the vulnerable fileSearch the web root directory for the file book_history.php. This is the specific file containing the SQL injection vulnerability.Affected if book_history.php exists in the web application directory
-
Check if del_id parameter is processedExamine book_history.php source code to verify if the del_id parameter is received via GET or POST and used directly in SQL queries without proper sanitization or parameterized queries.Affected if The code shows del_id being used in SQL queries without prepared statements or input validation
-
Verify application is accessible and exposedConfirm the web application is accessible over HTTP/HTTPS and book_history.php is reachable via the web browser.Affected if The vulnerable file is publicly accessible and accepts user input through the del_id parameter
A user is affected if they have MAGESH-K21 Online-College-Event-Hall-Reservation-System version 1.0 installed with book_history.php accessible and the del_id parameter being processed without 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.
dbcve · scopedReplace dynamic SQL queries with parameterized statements/prepared statements. Implement proper input validation on the del_id parameter. If immediate patching is not possible, implement Web Application Firewall rules as a temporary mitigation.
- This vulnerability in Online College Event Hall Reservation System 1.0 has no vendor-provided patch or upgrade path.
- The vendor (MAGESH-K21) was contacted but did not respond to the disclosure.
- No fixed version or official patch has been released for this SQL injection vulnerability in book_history.php (parameter: del_id).
- Consider the following mitigations: 1) Implement input validation/sanitization on the del_id parameter in book_history.php before using it in SQL queries, 2) Use parameterized queries (prepared statements) instead of direct SQL concatenation, 3) Apply Web Application Firewall (WAF) rules to block SQL injection attempts, 4) If possible, disable or restrict access to the affected endpoint until a se
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2517 — 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-2024-2517 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