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

> A Cross-Site Request Forgery vulnerability in BigAnt Server allows attackers to trick users into performing unintended actions.

- **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:** 21 Mar 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-c7hm-9h34-5g4x

## What is CVE-2022-23349?

CVE-2022-23349 is a high-severity vulnerability in n/a, published on 21 Mar 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

BigAnt Software BigAnt Server v5.6.06 was discovered to contain a Cross-Site Request Forgery (CSRF).

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

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

It affects 1 product.


Products: Bigantsoft Bigant Server.

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

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

## Is CVE-2022-23349 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-0364](https://insights.sbomify.com/CVE-2025-0364/): BigAntSoft BigAnt Server Account Registration Bypass to File Upload RCE (critical 9.8)
- [CVE-2022-23346](https://insights.sbomify.com/CVE-2022-23346/): File upload in n/a (high 8.8)
- [CVE-2022-26281](https://insights.sbomify.com/CVE-2022-26281/): Missing authorization in n/a (high 7.5)
- [CVE-2022-23345](https://insights.sbomify.com/CVE-2022-23345/): Missing authorization in n/a (high 7.5)
- [CVE-2022-23347](https://insights.sbomify.com/CVE-2022-23347/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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