CVE-2025-12609VulnerabilityPublished 3 Nov 2025Updated 24 Feb 2026

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

Affects CodeAstro Gym Management SystemSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 06:26 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 30% 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: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

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 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-12609, organizations should first verify if they are running CodeAstro Gym Management System version 1.0 and restrict access to the /admin/update-progress.php endpoint to trusted administrators only. Employ web application firewalls (WAFs) with rules targeting SQL injection patterns on the affected parameters. Enforce strict authentication and authorization controls, including multi-factor authentication for admin accounts, to reduce the risk of credential compromise. Regularly audit and monitor logs for suspicious activity related to the vulnerable endpoint. Segregate the database with least privilege principles to limit the impact of a successful injection. Organizations should also engage with the vendor for updates or patches and plan for timely application once available. Finally, conduct security awareness training for administrators to recognize phishing or social engineering attempts that could lead to credential theft.

Description

A vulnerability was found in CodeAstro Gym Management System 1.0. Affected by this issue is some unknown functionality of the file /admin/update-progress.php. Performing a manipulation of the argument id/ini_weight results in sql injection. The attack may be initiated remotely. The exploit has been made public and could be used.

Impact

The SQL injection vulnerability in CodeAstro Gym Management System 1.0 can have significant impacts on organizations using this software. Exploitation could allow attackers to access sensitive customer data such as personal information, membership details, and progress records, violating confidentiality. Attackers could also alter or delete data, undermining data integrity and potentially disrupting gym operations and member services. Availability could be affected if attackers execute destructive queries or cause database errors. Since the vulnerability requires authenticated admin access, the risk is somewhat mitigated by the need for credential compromise; however, insider threats or credential theft could enable exploitation. The public disclosure of exploit code increases the risk of attacks, especially in environments with weak access controls or poor credential management. Organizations could face reputational damage, regulatory penalties related to data protection laws, and operational downtime. The impact is particularly relevant for gyms and fitness centers relying on this system for member management and progress tracking.

Summary

CVE-2025-12609 is a SQL injection vulnerability identified in version 1.0 of the CodeAstro Gym Management System, specifically within the /admin/update-progress.php endpoint. The vulnerability stems from insufficient input validation and sanitization of the id and ini_weight parameters, which are used in SQL queries to update user progress data. An attacker with authenticated access to the admin interface can manipulate these parameters to inject malicious SQL code, potentially allowing unauthorized reading, modification, or deletion of database records. The vulnerability is remotely exploitable without user interaction but requires high-level privileges, indicating that attackers must first compromise or have legitimate admin credentials. The CVSS 4.0 score of 5.1 (medium severity) reflects the balance between ease of exploitation and the requirement for authentication. While no known exploits are currently active in the wild, the public availability of exploit code increases the likelihood of exploitation attempts. The vulnerability affects only version 1.0 of the product, and no patches have been officially released yet. This flaw could lead to data breaches, loss of data integrity, and disruption of gym management operations, impacting both the service provider and its customers.

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