# CVE-2023-42321: Cross-site request forgery in n/a

> A CSRF vulnerability in iCMS allows remote attackers to execute arbitrary code via admin control panel files.

- **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:** 20 Sep 2023
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-44vr-phh9-75gf

## What is CVE-2023-42321?

CVE-2023-42321 is a high-severity vulnerability in n/a, published on 20 Sep 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 icmsdev iCMSv.7.0.16 allows a remote attacker to execute arbitrary code via the user.admincp.php, members.admincp.php, and group.admincp.php files.

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

## Which versions are affected by CVE-2023-42321?

It affects 1 product.


Products: Icmsdev Icms.

## How do I fix CVE-2023-42321?

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

## Is CVE-2023-42321 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-42322](https://insights.sbomify.com/CVE-2023-42322/): Information disclosure in n/a (critical 9.8)
- [CVE-2019-6259](https://insights.sbomify.com/CVE-2019-6259/): SQL injection in n/a (critical 9.8)
- [CVE-2018-18702](https://insights.sbomify.com/CVE-2018-18702/): SQL injection in n/a (critical 9.8)
- [CVE-2018-14514](https://insights.sbomify.com/CVE-2018-14514/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2018-12498](https://insights.sbomify.com/CVE-2018-12498/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-42321 and fix it if it is affected.

What it is: CVE-2023-42321 is a high-severity vulnerability in n/a, published on 20 Sep 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: There is no known exploitation of CVE-2023-42321 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-2023-42321/ (Markdown: https://insights.sbomify.com/CVE-2023-42321/index.md)
```

## Sources

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

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