CVE-2026-4615
Received Received - Intake
SQL Injection in SourceCodester Online Catering Reservation /search.php

Publication date: 2026-03-24

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was identified in SourceCodester Online Catering Reservation 1.0. Impacted is an unknown function of the file /search.php. Such manipulation of the argument rcode leads to sql injection. The attack may be performed from remote. The exploit is publicly available and might be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-24
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2026-03-24
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
sourcecodester online_catering_reservation 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-74 The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The CVE-2026-4615 vulnerability is a critical SQL injection flaw in the Online Catering Reservation V1.0 PHP application, specifically in the /search.php file.

It occurs because the rcode parameter is improperly handled and directly used in SQL queries without adequate input validation or sanitization.

This allows attackers to inject malicious SQL code remotely without authentication.

Exploitation techniques include Boolean-based blind injection, error-based injection, and time-based blind injection, which can lead to unauthorized database access, data leakage, data manipulation, full system compromise, and potential service disruption.


How can this vulnerability impact me? :

This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive data, manipulation or deletion of data, and potentially full system compromise.

It can also lead to service disruption, affecting the availability and reliability of the Online Catering Reservation system.

Since the exploit requires no authentication and can be performed remotely, it poses a significant security risk.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

[{'type': 'paragraph', 'content': 'This vulnerability can be detected by testing the vulnerable parameter `rcode` in the `/search.php` file for SQL injection flaws. Several SQL injection techniques can be used, including Boolean-based blind, error-based, and time-based injections.'}, {'type': 'list_item', 'content': "Boolean-based blind injection payload example: `rcode=234' OR NOT 6545=6545#`"}, {'type': 'list_item', 'content': "Error-based injection payload example for MySQL β‰₯ 5.6: `rcode=234' AND GTID_SUBSET(CONCAT(0x716a6a7871,(SELECT (ELT(8991=8991,1))),0x7170767071),8991)-- MHrt`"}, {'type': 'list_item', 'content': "Time-based blind injection payload example for MySQL β‰₯ 5.0.12: `rcode=234' AND (SELECT 6449 FROM (SELECT(SLEEP(5)))oAnc)-- yAqe`"}, {'type': 'paragraph', 'content': 'Additionally, the use of automated tools like sqlmap can confirm the presence of this SQL injection vulnerability by targeting the `rcode` parameter.'}] [1]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include:

  • Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection.
  • Apply strict input validation and filtering to ensure inputs conform to expected formats.
  • Minimize database user permissions by avoiding the use of high-privilege accounts (such as root or admin) for application database connections.
  • Conduct regular security audits to detect and address vulnerabilities promptly.

Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart