# CVE-2024-55271: Cross-site request forgery in n/a

> Attackers can trick authenticated users into modifying their profile data via CSRF in the Gym Management System user panel.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Feb 2026
- **Updated:** 17 Feb 2026
- **Also known as:** GHSA-9pq4-hhwq-2hcq

## What is CVE-2024-55271?

CVE-2024-55271 is a low-severity vulnerability in n/a, published on 17 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A Cross-Site Request Forgery (CSRF) vulnerability has been identified in phpgurukul Gym Management System 1.0. This issue is present in the profile update functionality of the User Panel, specifically the /profile.php endpoint.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2024-55271?

It affects 1 product.


Products: Phpgurukul Gym Management System.

## How do I fix CVE-2024-55271?

No fix has been published for CVE-2024-55271 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-55271 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-55271 exists.

Public exploit code:

- GYM management system using PHP and MYSQL (github_poc): https://github.com/shoaibalam112/CVE-2024-55271

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-55271 and fix it if it is affected.

What it is: CVE-2024-55271 is a low-severity vulnerability in n/a, published on 17 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-55271 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-55271/ (Markdown: https://insights.sbomify.com/CVE-2024-55271/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-55271
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-55271
- OSV: https://osv.dev/vulnerability/CVE-2024-55271

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-55271/
Summaries are generated and may contain mistakes; the official description above is the record.