# CVE-2022-38931: Server-side request forgery in n/a

> Remote attackers can force the application to make arbitrary requests via URL injection in the file upload function.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Sep 2022
- **Updated:** 28 May 2025
- **Also known as:** GHSA-jfwq-pfcr-9f47

## What is CVE-2022-38931?

CVE-2022-38931 is a high-severity server-side request forgery vulnerability in n/a, published on 20 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Server-Side Request Forgery (SSRF) in fetch_net_file_upload function of baijiacmsV4 v4.1.4 allows remote attackers to force the application to make arbitrary requests via injection of arbitrary URLs into the url parameter.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Baijiacms Project Baijiacms.

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

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

## Is CVE-2022-38931 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-35150](https://insights.sbomify.com/CVE-2022-35150/): File upload in n/a (critical 9.8)
- [CVE-2019-7568](https://insights.sbomify.com/CVE-2019-7568/): SQL injection in n/a (critical 9.8)
- [CVE-2018-16724](https://insights.sbomify.com/CVE-2018-16724/): SQL injection in n/a (critical 9.8)
- [CVE-2022-45942](https://insights.sbomify.com/CVE-2022-45942/): Command injection in n/a (high 8.8)
- [CVE-2018-10503](https://insights.sbomify.com/CVE-2018-10503/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38931 is a high-severity server-side request forgery vulnerability in n/a, published on 20 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-38931 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-2022-38931/ (Markdown: https://insights.sbomify.com/CVE-2022-38931/index.md)
```

## Sources

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

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