# CVE-2023-46468: juzawebCMS Injection vulnerability

> Remote attackers can execute arbitrary code via crafted files in juzawebCMS custom plugin functions.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Oct 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-h92m-4g9m-72vr

## What is CVE-2023-46468?

CVE-2023-46468 is a high-severity code injection vulnerability in n/a, published on 28 Oct 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An issue in juzawebCMS v.3.4 and before allows a remote attacker to execute arbitrary code via a crafted file to the custom plugin function.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

2 open source packages ship an affected version, including juzaweb/cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `juzaweb/cms` | Packagist | All versions to 3.4 | None |
| `juzaweb/cms` | Packagist | All versions to 3.4 | None |

Products: Juzaweb Juzaweb Cms.

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

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

## Is CVE-2023-46468 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-46468 is a high-severity code injection vulnerability in n/a, published on 28 Oct 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-46468 in the wild and no public exploit code.

Affected packages and fixed versions:
- juzaweb/cms (Packagist): affected all versions up to 3.4; no fix listed
- juzaweb/cms (Packagist): affected all versions up to 3.4; no fix listed

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-46468/ (Markdown: https://insights.sbomify.com/CVE-2023-46468/index.md)
```

## Sources

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

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