# CVE-2022-3943: ForU CMS cms_chip.php cross site scripting

> Remote attackers can inject malicious scripts via the name argument in cms_chip.php, potentially compromising user sessions.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Nov 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-7pvx-xp68-6vm5

## What is CVE-2022-3943?

CVE-2022-3943 is a low-severity cross-site scripting vulnerability in ForU CMS, published on 11 Nov 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in ForU CMS. It has been classified as problematic. Affected is an unknown function of the file cms_chip.php. The manipulation of the argument name leads to cross site scripting. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-213450 is the identifier assigned to this vulnerability.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-707 (Improper Neutralization)

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

It affects 1 product.


Products: Foru Cms Project Foru Cms.

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

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

## Is CVE-2022-3943 being exploited?

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

## Other vulnerabilities in ForU CMS

- [CVE-2024-0426](https://insights.sbomify.com/CVE-2024-0426/): ForU CMS cms_template.php sql injection (medium 6.3)
- [CVE-2024-0729](https://insights.sbomify.com/CVE-2024-0729/): ForU CMS cms_admin.php sql injection (medium 5.5)
- [CVE-2024-0425](https://insights.sbomify.com/CVE-2024-0425/): ForU CMS password recovery (medium 5.3)
- [CVE-2024-0728](https://insights.sbomify.com/CVE-2024-0728/): ForU CMS channel.php file inclusion (medium 4.7)
- [CVE-2023-5221](https://insights.sbomify.com/CVE-2023-5221/): ForU CMS index.php code injection (medium 4.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3943 is a low-severity cross-site scripting vulnerability in ForU CMS, published on 11 Nov 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-3943 in the wild and no public exploit code.

Affected product: ForU CMS. 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-3943/ (Markdown: https://insights.sbomify.com/CVE-2022-3943/index.md)
```

## Sources

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

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