# CVE-2022-30931: Cross-site request forgery in n/a

> Attackers can force authenticated users to perform unwanted actions in the Employee Leaves Management System via CSRF.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-8w3p-594j-wqcj

## What is CVE-2022-30931?

CVE-2022-30931 is a medium-severity vulnerability in n/a, published on 14 Jun 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Employee Leaves Management System (ELMS) V 2.1 is vulnerable to Cross Site Request Forgery (CSRF) via /myprofile.php.

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

## Which versions are affected by CVE-2022-30931?

It affects 1 product.


Products: Employee Leaves Management System Project Employee Leaves Management System.

## How do I fix CVE-2022-30931?

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

## Is CVE-2022-30931 being exploited?

There is no known exploitation of CVE-2022-30931 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-0641](https://insights.sbomify.com/CVE-2023-0641/): PHPGurukul Employee Leaves Management System changepassword.php weak password (low 3.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-30931 and fix it if it is affected.

What it is: CVE-2022-30931 is a medium-severity vulnerability in n/a, published on 14 Jun 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-30931 in the wild and no public exploit code.

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-2022-30931/ (Markdown: https://insights.sbomify.com/CVE-2022-30931/index.md)
```

## Sources

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

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