CVE-2026-5649
Received Received - Intake
SQL Injection in code-projects Admission System Endpoint Allows Remote Exploit

Publication date: 2026-04-06

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability has been found in code-projects Online Application System for Admission 1.0. This issue affects some unknown processing of the file /enrollment/admsnform.php of the component Endpoint. Such manipulation leads to sql injection. The attack can be executed remotely. The exploit has been disclosed to the public and may be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-06
Last Modified
2026-04-29
Generated
2026-05-06
AI Q&A
2026-04-06
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
code-projects online_application_system 1.0
code-projects online_application_system_for_admission 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?

CVE-2026-5649 is a SQL Injection vulnerability found in the Online Application System for Admission version 1.0, specifically in the admission form processing endpoint at /enrollment/admsnform.php.

The vulnerability arises because the 'detid' parameter, which is submitted via HTTP POST, is directly concatenated into SQL queries without proper input validation or sanitization.

This unsafe SQL query construction allows attackers to inject arbitrary SQL code, potentially manipulating the database.

For example, an attacker can submit a payload that causes the database to execute a time delay, confirming the injection is successful.


How can this vulnerability impact me? :

Successful exploitation of this vulnerability can allow attackers to execute arbitrary SQL commands on the backend database.

  • Extract sensitive data from the database.
  • Bypass authentication mechanisms.
  • Modify or delete database records.
  • Escalate privileges within the system.
  • Potentially achieve full compromise of the backend database depending on database user permissions.

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

This vulnerability can be detected by testing the vulnerable endpoint `/OnlineApplicationSystem_PHP/enrollment/admsnform.php` for SQL injection via the `detid` parameter submitted through HTTP POST.

A common detection method is to use a time-based SQL injection payload to observe if the server response is delayed, indicating successful injection.

For example, submitting the following payload in the `detid` POST parameter can confirm the vulnerability by causing a delay of approximately 20 seconds:

  • detid='+(select*from(select(sleep(20)))a)+'

You can use tools like curl or Burp Suite to send this POST request and observe response times.

Example curl command to test the vulnerability:

  • curl -X POST -d "detid='+(select*from(select(sleep(20)))a)+'" https://targetsite/OnlineApplicationSystem_PHP/enrollment/admsnform.php -v

What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include:

  • Implement prepared statements with parameterized queries to safely handle the `detid` parameter instead of directly concatenating user input into SQL queries.
  • Validate and sanitize all user inputs to ensure they conform to expected formats, such as numeric IDs.
  • Apply the principle of least privilege to the database user accounts to limit the impact of any potential exploitation.
  • Conduct regular security testing, including code audits and penetration testing, to identify and fix similar vulnerabilities.

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

The SQL Injection vulnerability in the Online Application System for Admission allows attackers to execute arbitrary SQL commands, extract sensitive data, and potentially fully compromise the backend database. Such unauthorized access and data manipulation can lead to breaches of confidentiality, integrity, and availability of personal and sensitive information.

This kind of vulnerability can negatively impact compliance with common standards and regulations such as GDPR and HIPAA, which require protection of personal data and sensitive health information. Exploitation of this vulnerability could result in unauthorized disclosure or alteration of protected data, leading to regulatory violations, legal consequences, and loss of trust.


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