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

CVE-2024-2523

MEDIUM · 6.1 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 →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 problematic was found in MAGESH-K21 Online-College-Event-Hall-Reservation-System 1.0. This vulnerability affects unknown code of the file /admin/booktime.php. The manipulation of the argument id leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-256960. 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

A reflected cross-site scripting (XSS) vulnerability exists in the /admin/booktime.php file of the Online-College-Event-Hall-Reservation-System 1.0. The 'id' parameter is not properly sanitized, allowing an attacker to inject malicious JavaScript that executes in the victim's browser when they access the crafted URL.

MitigationImplement proper input validation and output encoding for the 'id' parameter in booktime.php. Use context-appropriate escaping functions and consider implementing a Content Security Policy (CSP) header as a defense-in-depth measure.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 version
    Locate and inspect the source files of the Magesh K21 Online College Event Hall Reservation System. Check any version files, README, or metadata that indicates the installed version. If using a package manager, run 'composer show' or similar to list installed package versions.
    Affected if The installed version is exactly 1.0 (this is the only affected version per vendor scope)
  2. Verify booktime.php exists in /admin/
    Check the web root directory for the presence of the /admin/booktime.php file. On the server, run: ls -la /path/to/webroot/admin/booktime.php or navigate to the equivalent directory path.
    Affected if The file /admin/booktime.php exists in the web application installation directory
  3. Confirm the admin interface is accessible
    Verify the web server is running and the /admin/ endpoint is reachable. Attempt to access the application's admin panel via HTTP/HTTPS to confirm the application is live and accessible to users.
    Affected if The application is running and the /admin/ directory is accessible over the network (the XSS requires a victim to visit a crafted URL)
  4. Inspect the id parameter handling in booktime.php
    Open /admin/booktime.php in a text editor or use 'grep' to search for the 'id' parameter usage: grep -n 'id' /path/to/webroot/admin/booktime.php. Examine the code around lines where $_GET['id'] or $_POST['id'] is used to see if the value is output directly to HTML without sanitization functions such as htmlspecialchars() or htmlentities().
    Affected if The code directly outputs the 'id' parameter value to HTML without proper input validation or output encoding (vulnerable code would show the parameter printed without escaping)
  5. Test for XSS via the id parameter
    If permitted and safe within your own environment, send a crafted request to the endpoint: http://yourdomain.com/admin/booktime.php?id=<script>alert('XSS')</script>. Use browser developer tools or a proxy to observe whether the script tag is reflected unescaped in the response HTML.
    Affected if The id parameter value is reflected in the response HTML without encoding, causing the script to execute in the browser

You are affected if you are running version 1.0 of the Magesh K21 Online College Event Hall Reservation System, the /admin/booktime.php file exists, and the 'id' parameter in that file is handled without sanitization or output encoding.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding for the 'id' parameter in booktime.php. Use context-appropriate escaping functions and consider implementing a Content Security Policy (CSP) header as a defense-in-depth measure.

Recommended fix Low confidence
  1. This vulnerability has no vendor-supplied patch as the vendor did not respond to the disclosure.
  2. As a mitigating control, implement output encoding/validation on the 'id' parameter in /admin/booktime.php before reflecting it in HTML.
  3. Apply web application firewall (WAF) rules to detect and block XSS payloads in the 'id' parameter.
  4. Restrict admin panel access to trusted IP addresses using network-level ACLs.
  5. Consider migrating to an actively maintained event reservation system that receives security updates.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Online College Event Hall Reservation System Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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