# CVE-2021-33396: Cross-site request forgery in n/a

> Attackers can exploit CSRF in baijiacms to change passwords or modify account information for arbitrary users.

- **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:** 15 Feb 2023
- **Updated:** 20 Mar 2025
- **Also known as:** CVE-2021-34250, GHSA-hx85-xr64-jmwv

## What is CVE-2021-33396?

CVE-2021-33396 is a medium-severity vulnerability in n/a, published on 15 Feb 2023. 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

Cross Site Request Forgery (CSRF) vulnerability in baijiacms 4.1.4, allows attackers to change the password or other information of an arbitrary account via index.php.

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

## Which versions are affected by CVE-2021-33396?

It affects 1 product.


Products: Baijiacms Project Baijiacms.

## How do I fix CVE-2021-33396?

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

## Is CVE-2021-33396 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-33396 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-2022-38931](https://insights.sbomify.com/CVE-2022-38931/): Server-side request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-33396 and fix it if it is affected.

What it is: CVE-2021-33396 is a medium-severity vulnerability in n/a, published on 15 Feb 2023. An attacker can exploit it over the internet without logging in, 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-2021-33396 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-2021-33396/ (Markdown: https://insights.sbomify.com/CVE-2021-33396/index.md)
```

## Sources

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

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