CVE-2021-42667 in the critical feed json
A SQL Injection vulnerability exists in Sourcecodester Online Event Booking and Reservation System in PHP in event-management/views.
published 2021-11-05 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-29628
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 16.2%
- EPSS 16.2% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
A SQL Injection vulnerability exists in Sourcecodester Online Event Booking and Reservation System in PHP in event-management/views. An attacker can leverage this vulnerability in order to manipulate the sql query performed. As a result he can extract sensitive data from the web server and in some cases he can use this vulnerability in order to get a remote code execution on the remote web server.
Exploit prediction
16.17% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template Online Event Booking and Reservation System 2.3.0 - SQL Injection nuclei detection template
- github.com https://github.com/TheHackingRabbi/CVE-2021-42667 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/nu11secur1ty/CVE-mitre/tree/main/CVE-2021-42667 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/TheHackingRabbi/CVE-2021-42667
exploit, third-party-advisory
-
github.com
/nu11secur1ty/CVE-mitre/tree/main/CVE-2021-42667
exploit, third-party-advisory
-
sourcecodester.com
/php/14241/online-event-booking-and-reservation-system-phpmysql.html
product, third-party-advisory
Sources
- CVE List CVE-2021-42667
- NVD CVE-2021-42667
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.