CVE-2025-12261VulnerabilityPublished 27 Oct 2025Updated 24 Feb 2026

CVE-2025-12261: 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.4% chance of exploitation in 30 days – higher than 38% 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 27 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

1. Immediately restrict access to the /admin/actions/remove-announcement.php endpoint to trusted administrators only, ideally via network segmentation or VPN. 2. Implement strict input validation and sanitization on all parameters, especially the ID parameter, using allowlists and rejecting unexpected input formats. 3. Employ parameterized queries or prepared statements in the application code to prevent SQL injection. 4. Monitor logs for suspicious database queries or repeated access attempts to the vulnerable endpoint. 5. Enforce strong authentication and access control policies to minimize the risk of privilege abuse. 6. Regularly audit and update the CodeAstro Gym Management System software, applying vendor patches promptly once available. 7. Consider deploying Web Application Firewalls (WAFs) with rules to detect and block SQL injection attempts targeting this endpoint. 8. Conduct security training for administrators to recognize and report suspicious activities. 9. Backup databases regularly to enable recovery in case of data tampering or loss.

Description

A vulnerability was found in CodeAstro Gym Management System 1.0. This affects an unknown function of the file /admin/actions/remove-announcement.php. Performing a manipulation of the argument ID results in sql injection. The attack can be initiated remotely. The exploit has been made public and could be used.

Impact

The SQL injection vulnerability could allow attackers with limited privileges to execute arbitrary SQL commands on the backend database, potentially leading to unauthorized disclosure of sensitive information such as user data, membership details, and financial records. Attackers might also alter or delete data, impacting data integrity and disrupting gym management operations. The availability of the system could be affected if attackers execute commands that cause database errors or crashes. For organizations, this could result in reputational damage, regulatory penalties due to data breaches, and operational downtime. Since the vulnerability requires some level of privilege, the impact is somewhat contained but still significant, especially if privilege escalation or credential compromise occurs. The public availability of exploit code increases the risk of automated attacks targeting vulnerable installations worldwide.

Summary

CVE-2025-12261 is an SQL injection vulnerability identified in CodeAstro Gym Management System version 1.0. The vulnerability exists in the /admin/actions/remove-announcement.php file, where the ID parameter is improperly sanitized, allowing an attacker to inject malicious SQL code. This injection flaw can be exploited remotely without user interaction but requires low-level privileges (PR:L), indicating that some form of authentication or limited privilege is necessary. The vulnerability impacts the confidentiality, integrity, and availability of the system’s backend database by enabling unauthorized data retrieval, modification, or deletion. The CVSS 4.0 base score is 5.3 (medium), reflecting the moderate risk due to the requirement of privileges and limited scope of impact. The attack complexity is low, and no user interaction is needed, increasing the likelihood of exploitation once credentials or access are obtained. Although no known exploits in the wild have been reported, the public disclosure of the exploit code increases the risk of future attacks. The vulnerability is critical for organizations relying on this gym management software, as it could lead to data breaches, unauthorized administrative actions, or disruption of service. The absence of vendor patches at the time of disclosure necessitates immediate defensive measures to mitigate risk.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats