CVE-2025-11589VulnerabilityPublished 10 Oct 2025Updated 24 Feb 2026

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

Affects CodeAstro Gym Management SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.3Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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: Low
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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 10 Oct 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

Organizations should immediately audit their use of CodeAstro Gym Management System 1.0 and restrict access to the /admin/user-payment.php functionality to trusted personnel only. Implement web application firewall (WAF) rules to detect and block SQL injection patterns targeting the 'plan' parameter. Employ strict input validation and parameterized queries or prepared statements in the application code to prevent injection. Monitor logs for suspicious database queries or unusual admin activity. If possible, isolate the affected system from external networks or restrict network access to trusted IPs. Engage with the vendor for patches or updates and apply them promptly once available. Conduct regular security assessments and penetration testing focused on SQL injection vectors. Educate administrators about the risks of low-privileged account compromise and enforce strong authentication and access controls. Consider database-level protections such as least privilege for database users and query anomaly detection. Maintain backups to enable recovery in case of data tampering or loss.

Description

A security flaw has been discovered in CodeAstro Gym Management System 1.0. Affected is an unknown function of the file /admin/user-payment.php. Performing a manipulation of the argument plan results in sql injection. It is possible to initiate the attack remotely. The exploit has been released to the public and may be used for attacks.

Impact

The SQL injection vulnerability can lead to unauthorized disclosure of sensitive data such as payment details and user information, undermining confidentiality. Attackers might alter or delete database records, affecting data integrity and potentially disrupting gym operations or billing processes. Availability could be impacted if attackers execute destructive queries or cause database errors. Organizations worldwide using CodeAstro Gym Management System 1.0 face risks of data breaches, financial fraud, and operational downtime. The presence of a public exploit increases the risk of automated or targeted attacks. Compromise could result in regulatory penalties, loss of customer trust, and financial losses. The requirement for low privileges limits the attack surface but does not eliminate risk, especially if low-privileged accounts are compromised or if insider threats exist. The medium severity rating reflects the moderate but tangible risk posed by this vulnerability.

Summary

CVE-2025-11589 identifies a SQL injection vulnerability in CodeAstro Gym Management System version 1.0, located in the /admin/user-payment.php file. The vulnerability stems from insufficient input validation or sanitization of the 'plan' parameter, which is used in SQL queries without proper escaping or parameterization. This allows an attacker with low privileges to remotely inject malicious SQL code, potentially manipulating the database to extract sensitive information, modify records, or disrupt service availability. The attack vector is network accessible (AV:N), requires low complexity (AC:L), no authentication (AT:N), and no user interaction (UI:N), but low privileges (PR:L) are needed, indicating that an attacker must have some level of access, such as a low-privileged admin or authenticated user. The impact on confidentiality, integrity, and availability is limited but present (VC:L, VI:L, VA:L). The vulnerability has a CVSS 4.0 base score of 5.3, categorized as medium severity. Although no known active exploits have been reported, a public exploit is available, increasing the likelihood of exploitation. No official patches or fixes have been released by the vendor, leaving systems exposed. This vulnerability is critical for organizations relying on this gym management software to protect customer payment and membership data. Attackers could leverage this flaw to compromise financial records or user information, leading to reputational damage and regulatory consequences.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 21:30 UTC

Technical details

References

Community reviews

Related threats