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

> Attackers can exploit CSRF in savepage.php to execute arbitrary code on u5cms installations.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 3 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-vgpw-v682-5grc

## What is CVE-2022-34937?

CVE-2022-34937 is a high-severity vulnerability in n/a, published on 3 Aug 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

Yuba u5cms v8.3.5 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component savepage.php. This vulnerability allows attackers to execute arbitrary code.

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

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

It affects 1 product.


Products: Yuba U5cms.

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

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

## Is CVE-2022-34937 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-1576](https://insights.sbomify.com/CVE-2015-1576/): SQL injection in n/a (high 7.5)
- [CVE-2015-1577](https://insights.sbomify.com/CVE-2015-1577/): Path traversal in n/a (medium 6.4)
- [CVE-2022-32442](https://insights.sbomify.com/CVE-2022-32442/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2022-32444](https://insights.sbomify.com/CVE-2022-32444/): Open redirect in n/a (medium 6.1)
- [CVE-2015-1578](https://insights.sbomify.com/CVE-2015-1578/): Open redirect in n/a (medium 5.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-34937 is a high-severity vulnerability in n/a, published on 3 Aug 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-34937 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-34937/ (Markdown: https://insights.sbomify.com/CVE-2022-34937/index.md)
```

## Sources

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

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