CVE-2022-2745
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 · uneditedA vulnerability, which was classified as critical, was found in SourceCodester Gym Management System. This affects an unknown part of the file /admin/add_trainers.php of the component Add New Trainer. The manipulation of the argument trainer_name leads to sql injection. It is possible to initiate the attack remotely. The identifier VDB-206013 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 · moderate confidenceA SQL injection vulnerability exists in SourceCodester Gym Management System's /admin/add_trainers.php file. The trainer_name parameter is not properly sanitized, allowing an attacker to inject malicious SQL queries. This can lead to unauthorized database access, data exfiltration, or potential remote code execution depending on the database configuration.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Gym Management System is installedLocate the web application directory and identify the presence of SourceCodester Gym Management System files, particularly in the /admin/ directoryAffected if The application files exist on the system
-
Identify the affected PHP fileVerify that /admin/add_trainers.php exists in the web application directoryAffected if The file add_trainers.php is present in the /admin/ folder
-
Check admin access to the vulnerable endpointAttempt to access the /admin/add_trainers.php page via HTTP request to confirm the admin panel is reachableAffected if The admin interface and add_trainers.php endpoint are accessible
-
Inspect trainer_name parameter handlingExamine the source code of add_trainers.php and locate the PHP code handling the trainer_name POST parameter. Look for direct use of $_POST['trainer_name'] in SQL queries without sanitization functions like htmlspecialchars, mysqli_real_escape_string, or prepared statementsAffected if The trainer_name parameter is used directly in SQL queries without parameterized queries or proper sanitization
-
Verify database interaction existsConfirm the application connects to a MySQL/MariaDB database and the add_trainers.php file performs database operations using trainer_name inputAffected if The application uses a database and trainer_name is incorporated into SQL statements without prepared statements
A user is affected if the Gym Management System is running with /admin/add_trainers.php accessible and the trainer_name parameter is used in unsanitized SQL queries.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement parameterized queries (prepared statements) for the trainer_name parameter and all user inputs in add_trainers.php to prevent SQL injection.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2745 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-2745 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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