CVE-2025-11590
BaseFortify
Publication date: 2025-10-11
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 |
|---|---|---|
| codeastro | gym_management_system | 1.0 |
Helpful Resources
Exploitability
| 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-2025-11590 is a critical SQL injection vulnerability in CodeAstro Gym Management System version 1.0, specifically in the file /admin/equipment-entry.php. The vulnerability occurs because the 'ename' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can lead to unauthorized access to the database, enabling attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can allow attackers to gain unauthorized access to your database, leading to data leakage, data tampering, and potential disruption of services. Attackers could modify or delete data, retrieve sensitive information, and potentially gain full control over the system. The exploit is publicly available and can be executed remotely, increasing the risk of compromise. [1, 2, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability can negatively impact compliance with standards such as GDPR and HIPAA because it risks unauthorized access to sensitive personal and health-related data. A successful SQL injection attack could lead to data breaches, violating data protection requirements and potentially resulting in legal and financial penalties. [1, 2, 3]
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 'ename' parameter in the /admin/equipment-entry.php file for SQL injection. A time-based blind SQL injection test can be performed using payloads such as: ename=123' AND (SELECT 1542 FROM (SELECT(SLEEP(5)))QGZq) AND 'kzLT'='kzLT. Additionally, tools like sqlmap can be used to automate detection by sending crafted POST requests to /Gym-System/admin/add-equipment-req.php with the vulnerable 'ename' parameter. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Using prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input; 2) Implementing strict input validation and filtering to ensure inputs conform to expected formats; 3) Limiting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations; 4) Conducting regular security audits of code and systems to detect and address vulnerabilities promptly. If possible, replacing the affected component with an alternative product is also suggested. [2, 3]