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

> An unauthenticated attacker can trick administrators into performing unintended actions, leading to content modification or deletion in Shopxian CMS.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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:** 13 Sep 2022
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-cc6x-6938-549x

## What is CVE-2022-38329?

CVE-2022-38329 is a medium-severity vulnerability in n/a, published on 13 Sep 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

A CSRF vulnerability in Shopxian CMS 3.0.0 could allow an unauthenticated, remote attacker to craft a malicious link, potentially causing the administrator to perform unintended actions on an affected system. The vulnerability could allow attackers to modify or delete specific content through crafted requests, potentially leading to data loss and system integrity issues.

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

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

It affects 1 product.


Products: Shopxian Shopxian Cms.

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

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

## Is CVE-2022-38329 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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