dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-67147

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Multiple SQL injection vulnerabilities exist in amansuryawanshi Gym-Management-System-PHP 1.0 across three PHP files (submit_contact.php, secure_login.php, and change_s_pwd.php) affecting nine distinct input parameters. Unauthenticated attackers can exploit these to bypass authentication and execute arbitrary SQL commands, potentially achieving full database compromise and administrator privilege escalation.

MitigationReplace all dynamic SQL queries in the affected files with parameterized queries/prepared statements, implement strict input validation, and apply the principle of least privilege to the database user account.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the Gym-Management-System-PHP application is present
    Search the web server document root for the file structure typical of this application, particularly looking for directories containing gym management code
    Affected if The application codebase exists on the server
  2. Identify the installed version
    Check for a version file, README, or any file within the application that states the version number; also check composer.json or similar if present
    Affected if The version is 1.0 or if the version cannot be determined and the application appears to be this specific system
  3. Locate the affected PHP files
    Verify the presence of submit_contact.php, secure_login.php, and change_s_pwd.php in the application directory structure, typically found in the root or admin folder
    Affected if Any of these three files exist in the application
  4. Inspect vulnerable parameters in submit_contact.php
    Open submit_contact.php and examine the handling of input parameters for SQL query construction without prepared statements; look for direct insertion of POST/GET parameters into SQL queries
    Affected if The code shows dynamic SQL with unsanitized user input from contact form fields
  5. Inspect vulnerable parameters in secure_login.php
    Open secure_login.php and examine login-related parameters (username, password, or similar) being used directly in SQL queries without parameterization
    Affected if The login processing code builds SQL queries using raw user credentials or other login inputs
  6. Inspect vulnerable parameters in change_s_pwd.php
    Open change_s_pwd.php and examine password change functionality for SQL query construction using unsanitized user-supplied values
    Affected if The password change logic constructs SQL statements with unvalidated input

A user is affected if they are running amansuryawanshi Gym-Management-System-PHP version 1.0 and the three affected PHP files (submit_contact.php, secure_login.php, change_s_pwd.php) are present with unauthenticated SQL injection vulnerabilities in their parameter handling.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace all dynamic SQL queries in the affected files with parameterized queries/prepared statements, implement strict input validation, and apply the principle of least privilege to the database user account.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67147 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-67147 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data