Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRequest predictable /database/medallion.sql URL
-
ExploitServer returns raw SQL file
-
ExecutionHarvest schema and sensitive data
-
ImpactPlan follow-on attacks (e.g. SQLi/credential reuse)
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Sensitive file access control
|
| Exploitation Conditions | Exploitation requires that the /database/medallion.sql file be deployed within the web-accessible document root and served as a static file by the web server (the default layout of this application, where the database bootstrap SQL ships alongside the PHP code). No authentication, user interaction, or special configuration is required per the CVSS vector (PR:N/UI:N/AC:L). The practical LIMITING factors are: the server must not be configured to deny access to .sql files (many hardened or production deployments block or relocate such files outside the web root), and the attacker must know or guess the path - which the public POC supplies. Impact is confined to information disclosure (schema/structure and any data embedded in the SQL dump); it does not by itself grant write access or code execution. |
| Impact | This is a high-CVSS-label-but-low-real-risk issue in practice. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes a remotely reachable, low-complexity, unauthenticated flaw, but the only impact is low confidentiality (VC:L, with VI:N/VA:N), consistent with CWE-538 file/directory information exposure - exposure of a SQL file (/database/medallion.sql) rather than code execution or data modification. Exploitation status is 'publicly available exploit code exists' (POC on GitHub, reported by VulDB); there is NO CISA KEV listing and NO EPSS score provided, so there is no evidence of active or widespread exploitation. The input CVSS 4.0 includes E:P (Proof-of-Concept exploit maturity), which aligns with the public POC but again does not indicate in-the-wild use. The practical risk is modest: the affected product (code-projects Online Ticket Reservation System 1.0) is a small open-source/student-grade PHP application with negligible enterprise deployment, so this is a low-priority, information-disclosure-only issue for the overwhelming majority of organizations. No SSVC decision data was provided in the input. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker requests the predictable path /database/medallion.sql directly from the web server and retrieves the application's SQL file, revealing database schema, table/column names, and potentially seeded credentials or structure. A public POC exists (GitHub, KaranParelkar), lowering the effort required. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, no authentication, user interaction, or special timing is needed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Information exposure in code-projects Online Ticket Reservation System 1.0 allows an unauthenticated, remote attacker to fetch the raw database bootstrap file /database/medallion.sql directly over HTTP and read the embedded schema and any seed data it contains. The path is trivial to guess and publicly available exploit code exists (published via a GitHub proof-of-concept referenced from the VulDB entry), though there is no confirmed evidence of active exploitation in the wild and the attack requires the .sql file to sit inside the web-accessible document root with .sql requests not blocked. Impact is limited to confidentiality loss - schema and content disclosure only, with no write access or code execution - so despite a CVSS 4.0 base score of 5.5, the practical business risk is comparatively low.
RemediationAI
No vendor-released patch was identified at time of analysis, so remediation must be handled at the deployment layer. The primary fix is to move the database directory (in particular /database/medallion.sql) outside the web document root or delete it from production servers after installation, which fully removes the exposure with no functional trade-off once the application is provisioned; note that removing it prematurely will break any browser-driven installer step that reads the dump. If the file must remain in place, deny static access to SQL artifacts at the web server - for Apache add a FilesMatch block rejecting *.sql requests, and for nginx add a location rule returning 403 for \.sql$ - accepting the caveat that any legitimate HTTP-based setup routine will also be blocked and must be run from the command line instead. Because the content may already have been read by attackers, treat the dump as disclosed: review it for embedded database credentials or tokens and rotate them, and compare live schema against the dump for unauthorized changes. Additional hardening includes placing the application behind an authenticating reverse proxy or WAF rule that rejects requests for backup, schema, and configuration paths, while acknowledging that such a layer adds operational overhead and can be bypassed by encoding tricks. Monitor logs for GET requests to /database/medallion.sql or similar .sql paths as an indicator of scanning activity.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-538 (File and Directory Information Exposure) describes the root cause: sensitive artifacts are stored inside the web document root and served by the web server as ordinary static content, without any authorization check. Code-projects' PHP applications ship their database initialization script (medallion.sql) alongside the deployed PHP sources under /database/, and because the web server treats .sql as a static MIME type rather than a script, a plain GET request returns the complete file. Nothing in the request flow reaches application code, so no session, token, or authentication is involved (CVSS vector PR:N/UI:N). The CPE cpe:2.3:a:code-projects:online_ticket_reservation_system:*:*:*:*:*:*:*:* confirms the affected product family without pinning a patched or fixed version, consistent with a project that has no coordinated release process. The disclosed content is whatever the developer committed to the dump - table DDL, default or seed rows, and potentially credentials or configuration values - which makes this a reconnaissance-enabling leak rather than a direct compromise primitive.
Know when Online Ticket Reservation System gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
Remotely requestable static SQL file needing no auth or interaction (AV:N/AC:L/PR:N/UI:N); only limited confidentiality disclosure, no integrity or availability impact (C:L/I:N/A:N, S:U).
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
2DescriptionCVE.org
A vulnerability was detected in code-projects Online Ticket Reservation System 1.0. This vulnerability affects unknown code of the file /database/medallion.sql. The manipulation results in file and directory information exposure. It is possible to launch the attack remotely. The exploit is now public and may be used.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-98082
GHSA-f24m-vxwf-fc9r
NVD
CVE.org
EPSS
VulDB
Exploit-DB