CVE-2025-67146
Multiple SQL Injection in GYM-MANAGEMENT-SYSTEM 1.0 Enables Data Breach
Publication date: 2026-01-12
Last updated on: 2026-01-12
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| abhishek_mali21 | gym_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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves multiple SQL Injection issues in the Gym Management System. Specifically, the application does not properly sanitize user inputs in several PHP files (member_search.php, trainer_search.php, gym_search.php, payment_search.php, and update_member.php). Attackers can inject malicious SQL commands via the 'name' or 'id' parameters, allowing them to manipulate database queries. For example, by sending crafted input like ' OR 1=1 -- -, an attacker can bypass filters and retrieve all records from the database. [1]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized extraction of sensitive data, bypassing authentication mechanisms, and modification of database contents. An unauthenticated remote attacker can exploit these SQL Injection flaws to access confidential information, alter records, or disrupt the normal operation of the Gym Management System. [1]
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 parameters with SQL injection payloads. For example, sending a payload such as `' OR 1=1 -- -` in the 'name' parameter on the search pages (e.g., member_search.php) can confirm the SQL injection vulnerability if it returns all records. You can use tools like curl or sqlmap to test these endpoints. Example curl command: curl -X POST -d "name=' OR 1=1 -- -" http://targetsite/member_search.php Similarly, test trainer_search.php, gym_search.php with the 'name' parameter and payment_search.php with the 'id' parameter using similar payloads. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing parameterized queries (prepared statements) using mysqli_prepare to separate SQL code from user input, thereby preventing SQL injection. Avoid directly concatenating user input into SQL queries. Additionally, review and sanitize all user inputs in the affected PHP files (member_search.php, trainer_search.php, gym_search.php, payment_search.php, update_member.php) to prevent injection attacks. [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthenticated attackers to perform SQL injection attacks that can lead to unauthorized data extraction, modification, or authentication bypass. Such unauthorized access and potential data breaches can result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and ensuring data integrity and confidentiality. [1]