VulnerabilityPublished 3 Nov 2025Updated 24 Feb 2026

CVE-2025-12610: CodeAstro Gym Management System · SQL Injection

Affects CodeAstro Gym Management SystemSource CVE Database V5

Public exploit available · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
CodeAstro Gym Management System	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2025-12610, organizations should first seek official patches or updates from CodeAstro once available. In the absence of patches, immediate steps include auditing and restricting access to the /admin/view-progress-report.php functionality to only trusted, authenticated users with necessary privileges. Implement input validation and sanitization on the 'ID' parameter, preferably by using prepared statements or parameterized queries to prevent SQL injection. Conduct thorough code reviews and penetration testing focused on SQL injection vectors. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious SQL injection attempts targeting this endpoint. Monitor logs for unusual database query patterns or failed injection attempts. Additionally, enforce strong authentication and session management controls to reduce the risk of compromised credentials being used to exploit this vulnerability. Regular backups and incident response plans should be in place to recover from potential data manipulation or loss.

Description

A vulnerability was determined in CodeAstro Gym Management System 1.0. This affects an unknown part of the file /admin/view-progress-report.php. Executing a manipulation of the argument ID can lead to sql injection. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized.

Impact

The potential impact of CVE-2025-12610 includes unauthorized access to sensitive gym management data such as member progress reports, personal information, and administrative records. Attackers exploiting this vulnerability could manipulate SQL queries to read, modify, or delete data, potentially leading to data breaches, loss of data integrity, and disruption of gym management operations. Although the requirement for high privileges reduces the risk of external exploitation, insider threats or compromised accounts could leverage this vulnerability to escalate damage. The compromise of confidential member data could result in reputational damage, regulatory penalties, and loss of customer trust for affected organizations. Additionally, data manipulation could disrupt business processes, causing operational downtime or erroneous reporting. Organizations relying on this system should consider the risk to both data confidentiality and operational continuity.

Summary

CVE-2025-12610 is a SQL injection vulnerability identified in CodeAstro Gym Management System version 1.0, specifically within the /admin/view-progress-report.php script. The vulnerability stems from inadequate input validation and sanitization of the 'ID' parameter, which is used in SQL queries without proper escaping or parameterization. This flaw allows an authenticated attacker with high privileges to remotely inject malicious SQL code by manipulating the 'ID' argument, potentially altering the intended SQL commands executed by the database. The vulnerability does not require user interaction but does require authentication, limiting exposure to authorized users. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no user interaction (UI:N), and high privileges required (PR:H). The impact on confidentiality, integrity, and availability is low to medium, as the attacker could read or modify data but not necessarily escalate privileges or cause system-wide denial of service. No patches or fixes have been linked yet, and no known exploits are reported in the wild, but public disclosure increases the risk of exploitation attempts. This vulnerability highlights the importance of secure coding practices, especially input validation and use of prepared statements to prevent SQL injection.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:14 UTC

Technical details

References

Community reviews

Related threats