Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-67147: n/a

0
Critical
VulnerabilityCVE-2025-67147cvecve-2025-67147
Published: Mon Jan 12 2026 (01/12/2026, 00:00:00 UTC)
Source: CVE Database V5

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.

AI-Powered Analysis

AILast updated: 01/12/2026, 21:23:35 UTC

Technical Analysis

CVE-2025-67147 identifies multiple SQL Injection vulnerabilities in the Gym-Management-System-PHP version 1.0, a PHP-based web application designed for managing gym operations. The vulnerabilities reside in several input parameters across three key PHP scripts: submit_contact.php ('name', 'email', 'comment'), secure_login.php ('username', 'pass_key'), and change_s_pwd.php ('login_id', 'pwfield', 'login_key'). These parameters are improperly sanitized, allowing attackers to inject malicious SQL code. An attacker can exploit these flaws without authentication or with limited authentication, enabling them to bypass login mechanisms, execute arbitrary SQL commands, manipulate or delete database records, and escalate privileges to administrator level. This could lead to full system compromise, data leakage, and unauthorized control over the application. The lack of a CVSS score indicates that the vulnerability is newly published and not yet fully assessed, but the technical details suggest high risk. No patches or known exploits are currently reported, but the vulnerabilities' nature demands urgent attention. The attack surface includes user input fields commonly accessible to both authenticated and unauthenticated users, increasing the likelihood of exploitation. The vulnerabilities stem from inadequate input validation and the absence of parameterized queries or prepared statements in the affected PHP scripts.

Potential Impact

For European organizations using the Gym-Management-System-PHP 1.0, this vulnerability poses significant risks. Exploitation could lead to unauthorized access to sensitive personal data of gym members, including names, emails, and possibly payment information if stored in the database. Attackers could manipulate membership records, disrupt gym operations by deleting or altering data, and gain administrative privileges to control the system fully. This could result in service downtime, reputational damage, regulatory penalties under GDPR for data breaches, and financial losses. The ability to bypass authentication without credentials exacerbates the threat, making it easier for attackers to compromise systems remotely. Given the widespread use of PHP-based management systems in small to medium fitness centers across Europe, the impact could be broad. Additionally, compromised systems could be leveraged as pivot points for further attacks within organizational networks. The threat also raises concerns about data integrity and availability, critical for operational continuity in the fitness industry.

Mitigation Recommendations

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.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-12-08T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 696562ddda2266e83825f9fe

Added to database: 1/12/2026, 9:08:45 PM

Last enriched: 1/12/2026, 9:23:35 PM

Last updated: 1/12/2026, 10:47:50 PM

Views: 7

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats