dbcve.org
Gym Management SystemApplication · Gym Management System Project

CVE-2022-2708

CRITICAL · 9.8 CVSS v3.1 Published 2022-08-08
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
A vulnerability, which was classified as critical, was found in SourceCodester Gym Management System. This affects an unknown part of the file login.php. The manipulation of the argument user_login with the input [email protected]' OR (SELECT 9084 FROM(SELECT COUNT(*),CONCAT(0x7178767871,(SELECT (ELT(9084=9084,1))),0x71767a6271,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)-- dPvW leads to sql injection. Access to the local network is required for this attack. The exploit has been disclosed to the public and may be used. The identifier VDB-205833 was assigned to this vulnerability.

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

SQL injection vulnerability in SourceCodester Gym Management System's login.php page. The user_login parameter is directly incorporated into an SQL query without proper sanitization or parameterized statements, allowing an attacker to inject arbitrary SQL code. The provided payload demonstrates an error-based UNION injection technique using SELECT with ELT, COUNT, CONCAT, and GROUP BY to extract data from the database.

MitigationReplace direct string concatenation in SQL queries with prepared statements/parameterized queries. Implement strict input validation on the user_login parameter and apply principle of least privilege to database user accounts.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Gym Management SystemApplication
Affected:all versions

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. Locate the Gym Management System installation
    Search the web server document root for login.php and other PHP files belonging to the SourceCodester Gym Management System project
    Affected if The application files are present on the server
  2. Verify the login.php file exists and is accessible
    Confirm the presence of login.php in the application's web-accessible directory
    Affected if login.php exists in the web application root
  3. Inspect the login.php source code for the vulnerable user_login parameter
    Open login.php and search for occurrences of user_login within SQL query strings. Look for code that directly incorporates this parameter into a query without using prepared statements
    Affected if The code constructs SQL queries using direct concatenation with the user_login parameter (e.g., "SELECT * FROM users WHERE user_login='" . $_POST['user_login'] . "'")
  4. Confirm lack of prepared statement usage
    Check if the login.php file uses mysqli_prepare, PDO::prepare, or similar parameterized query functions when handling the user_login parameter
    Affected if No prepared statements or parameterized queries are used when querying the database with user_login data

If the Gym Management System is installed and its login.php directly incorporates the user_login parameter into SQL queries without prepared statements, the environment is affected by CVE-2022-2708.

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 direct string concatenation in SQL queries with prepared statements/parameterized queries. Implement strict input validation on the user_login parameter and apply principle of least privilege to database user accounts.

Fix this in Gym Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2708 — 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-2022-2708 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