CVE-2026-0700
SQL Injection in Intern Membership Management System Admin Panel
Publication date: 2026-01-08
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| code-projects | intern_membership_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-0700 is a SQL injection vulnerability in version 1.0 of the code-projects Intern Membership Management System, specifically in the file /intern/admin/check_admin.php. The vulnerability occurs because the Username parameter is not properly sanitized, allowing an attacker to manipulate SQL queries. This flaw enables remote attackers to execute arbitrary SQL commands without authentication, potentially compromising the system. [1, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to remotely execute SQL injection attacks, which can lead to unauthorized access to sensitive data, modification or deletion of data, and disruption of system availability. It affects the confidentiality, integrity, and availability of the system, making it a high severity risk. [1, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the vulnerable file `/intern/admin/check_admin.php` and testing the `Username` parameter for SQL injection. Attackers can identify vulnerable targets using Google dorking with the query `inurl:intern/admin/check_admin.php`. For detection on your system, you can attempt to send crafted HTTP requests to the `check_admin.php` script with SQL injection payloads in the `Username` parameter and observe if the system is vulnerable. Example command using curl to test for SQL injection: `curl -G 'http://target-site/intern/admin/check_admin.php' --data-urlencode 'Username=admin'` and then try with a payload like `' OR '1'='1` to see if the response indicates SQL injection vulnerability. [1]
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or mitigations have been identified for this vulnerability. It is recommended to replace the affected component with an alternative product to mitigate the risk. Immediate steps include restricting access to the vulnerable script, monitoring for exploitation attempts, and applying any available patches or updates if released by the vendor. [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized remote SQL injection attacks that can compromise the confidentiality, integrity, and availability of the system, potentially leading to unauthorized access and disclosure of sensitive data. Such data breaches can negatively impact compliance with standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive information. However, no specific compliance impact details are provided in the resources. [1, 3]