CVE-2025-12242
BaseFortify
Publication date: 2025-10-27
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-12242 is a critical SQL injection vulnerability in CodeAstro Gym Management System version 1.0, specifically in the file /admin/actions/check-attendance.php. The vulnerability occurs because the 'id' parameter is not properly validated or sanitized before being used in SQL queries, allowing attackers to inject malicious SQL code remotely without authentication. This can lead to unauthorized database access and manipulation. [1, 2, 4]
How can this vulnerability impact me? :
This vulnerability can allow attackers to remotely execute arbitrary SQL commands on the database, leading to unauthorized access, data leakage, data tampering, deletion or modification of data, full system control, and potential service disruption. It poses a serious threat to system security and business continuity. [1, 2, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The vulnerability can be detected by testing the 'id' parameter in the /admin/actions/check-attendance.php file for SQL injection. One method is to use time-based blind SQL injection payloads such as: id=11' AND (SELECT 5697 FROM (SELECT(SLEEP(5)))NaHl) AND 'XEVr'='XEVr' which causes a delay in the database response if vulnerable. Automated tools like sqlmap can be used to detect this vulnerability by targeting the URL with the vulnerable parameter. Additionally, Google dorking with queries like 'inurl:admin/actions/check-attendance.php' can help identify potentially vulnerable endpoints on your network. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Replace the affected component or upgrade to a version without the vulnerability if available. - Use prepared statements with parameter binding to prevent SQL injection. - Implement strict input validation and filtering on the 'id' parameter to ensure it conforms to expected formats. - Limit database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. - Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. [1, 2, 4]