CVE-2025-11591
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-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-2025-11591 is a critical SQL injection vulnerability in CodeAstro Gym Management System version 1.0, specifically in the file /admin/actions/delete-member.php. The vulnerability occurs because the 'id' parameter is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely, potentially manipulating the database by accessing, modifying, or deleting data without authorization. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, allowing attackers to leak sensitive information, tamper with or delete data, gain full control over the system, and cause service interruptions. This threatens the confidentiality, integrity, and availability of the system, potentially disrupting business operations and compromising system security. [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 URL parameter `id` in `/Gym-System/admin/actions/delete-member.php` for SQL injection. You can use tools like sqlmap to automate detection. Example sqlmap command: `sqlmap -u "http://target/Gym-System/admin/actions/delete-member.php?id=8" --batch --level=5 --risk=3`. Additionally, manual testing can be done using payloads such as boolean-based blind SQL injection: `id=(SELECT (CASE WHEN (5274=5274) THEN 8 ELSE (SELECT 7122 UNION SELECT 4000) END))` or time-based blind SQL injection: `id=8 AND (SELECT 8634 FROM (SELECT(SLEEP(5)))nCKR)`. Also, attackers may be identified by scanning for URLs matching `inurl:admin/actions/delete-member.php` using Google dorking to find vulnerable targets. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Enforce strict input validation and filtering on the `id` parameter to ensure it conforms to expected formats. 3) Minimize database user permissions by avoiding use of high-privilege accounts like root or admin for routine database operations. 4) Conduct regular security audits to detect and remediate vulnerabilities promptly. If possible, replace or update the affected component or product to a secure version. [1, 3]