dbcve.org
Online College Event Hall Reservation SystemApplication · Magesh K21

CVE-2024-2522

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 vulnerability classified as critical has been found in MAGESH-K21 Online-College-Event-Hall-Reservation-System 1.0. This affects an unknown part of the file /admin/booktime.php. The manipulation of the argument room_id leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-256959. 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 confidence

Critical SQL injection vulnerability in the Online-College-Event-Hall-Reservation-System 1.0 allows remote attackers to inject malicious SQL queries through the room_id parameter in /admin/booktime.php. The lack of parameterized queries or input sanitization enables attackers to manipulate database queries, potentially exfiltrating sensitive data, modifying records, or gaining further system access.

MitigationReplace dynamic SQL query construction with parameterized queries/prepared statements for the room_id parameter and all user inputs in booktime.php. Apply strict input validation, least-privilege database accounts, and consider a WAF as a temporary layer.

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
Online College Event Hall Reservation SystemApplication
Affected:= 1.0

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 the application is installed
    Locate the web root directory and search for the file /admin/booktime.php or the presence of the Online-College-Event-Hall-Reservation-System application files.
    Affected if The file /admin/booktime.php exists in the web application directory structure.
  2. Verify the application version
    Check version files, about pages, or any version indicator within the application. Common locations include a readme.txt, version.php, or footer/version info in the admin panel.
    Affected if The installed version is exactly 1.0.
  3. Inspect the vulnerable file
    Open /admin/booktime.php in a text editor and search for the room_id parameter handling. Look for SQL query construction that uses this parameter without prepared statements or parameter binding.
    Affected if The file contains dynamic SQL queries that incorporate the room_id parameter directly without parameterized queries or input sanitization.
  4. Check admin panel accessibility
    Verify that the /admin/ interface is accessible over the network. Attempt to access the login page or check if the application is exposed on a web server.
    Affected if The admin panel is accessible without additional authentication barriers or is exposed to untrusted networks.
  5. Test the parameter for injection potential
    If authorized and safe to do in a non-production environment, send a crafted request with SQL syntax in the room_id parameter (e.g., room_id=1' OR '1'='1) and observe database behavior or error responses.
    Affected if The application returns database errors or behaves differently based on SQL injection payloads in the room_id parameter.

A user is affected if the Online-College-Event-Hall-Reservation-System version 1.0 is installed with the /admin/booktime.php file present and accessible, and that file contains unauthenticated SQL query construction using the room_id parameter.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL query construction with parameterized queries/prepared statements for the room_id parameter and all user inputs in booktime.php. Apply strict input validation, least-privilege database accounts, and consider a WAF as a temporary layer.

Fix this in Online College Event Hall Reservation System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2522 — 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-2024-2522 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