Skip to main content
CVE-2025-67147VulnerabilityPublished

CVE-2025-67147: Gym-Management-System-PHP · n/a

Affects Gym-Management-System-PHPSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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-25.

What to do

Affected software

ProductAffectedFixed in
GitHubamansuryawanshi/Gym-Management-System-PHPpkg:github/amansuryawanshi/Gym-Management-System-PHPOther threatsAffected
  • =1.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate these vulnerabilities, organizations should immediately conduct a thorough security review of the Gym-Management-System-PHP 1.0 source code, focusing on the affected PHP scripts. Implement parameterized queries or prepared statements to prevent SQL injection attacks instead of directly embedding user input into SQL commands. Apply rigorous input validation and sanitization on all user-supplied data, especially for the parameters identified. Restrict database user permissions to the minimum necessary, avoiding administrative privileges for the application database user. If possible, isolate the database server from direct internet access and monitor logs for suspicious SQL activity. Organizations should also consider upgrading to a patched version once available or replacing the vulnerable system with a more secure alternative. Regular security training for developers and administrators on secure coding practices is recommended. Finally, implement web application firewalls (WAFs) with SQL injection detection rules as an additional protective layer.

Description

Multiple SQL Injection vulnerabilities exist in amansuryawanshi Gym-Management-System-PHP 1.0 via the 'name', 'email', and 'comment' parameters in (1) submit_contact.php, the 'username' and 'pass_key' parameters in (2) secure_login.php, and the 'login_id', 'pwfield', and 'login_key' parameters in (3) change_s_pwd.php. An unauthenticated or authenticated attacker can exploit these issues to bypass authentication, execute arbitrary SQL commands, modify database records, delete data, or escalate privileges to administrator level.

References

Community reviews

Loading reviews…