CVE-2022-2776
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 classified as problematic has been found in SourceCodester Gym Management System. Affected is an unknown function of the file delete_user.php. The manipulation of the argument delete_user leads to denial of service. It is possible to launch the attack remotely. The identifier of this vulnerability is VDB-206172.
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 denial of service vulnerability exists in SourceCodester Gym Management System's delete_user.php file. The delete_user parameter can be manipulated to cause denial of service. The specific exploitation mechanism and root cause are not detailed in the available description.
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
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 installationSearch the web server document root for the presence of SourceCodester Gym Management System files, particularly looking for index.php or other typical PHP application entry points.Affected if The application files are present on the server and accessible via web requests.
-
Locate delete_user.php fileCheck the application's web-accessible directories for the presence of delete_user.php file. Common paths may include /user/, /admin/, or the application root directory.Affected if The delete_user.php file exists in a web-accessible location.
-
Verify delete_user parameter is functionalSend an HTTP request to delete_user.php and observe if the delete_user parameter is processed. This may require checking the application's routing or direct access to the PHP file.Affected if The delete_user parameter is accepted and processed by the server without proper validation checks.
-
Test for missing rate limitingSend multiple rapid requests to the delete_user functionality and observe if the server imposes any throttling, request limits, or resource constraints.Affected if The server allows rapid or repeated requests without rate limiting or resource constraints.
-
Check for input validation on delete_user parameterReview the delete_user.php code or test the parameter with various inputs to determine if proper validation, sanitization, or authorization checks are implemented before processing.Affected if The delete_user parameter can be manipulated or accepts arbitrary values without validation or authorization enforcement.
A user is affected if they have the SourceCodester Gym Management System deployed with the delete_user.php file accessible and the delete_user parameter lacks proper input validation, authorization checks, and rate limiting protections.
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 proper input validation and authorization checks on the delete_user parameter in delete_user.php. Additionally, implement rate limiting and resource constraints to prevent denial of service conditions.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2776 — 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-2776 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