# CVE-2023-30148: Cross-site scripting in n/a

> Authenticated attackers can inject arbitrary scripts via specific fields in the Opart multihtmlblock plugin, potentially compromising user sessions.

- **Severity:** Medium 6.1 (`CVSS:3.1/AC:L/AV:N/A:N/C:H/I:H/PR:H/S:U/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Oct 2023
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-7v28-76v4-349r

## What is CVE-2023-30148?

CVE-2023-30148 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 Oct 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Multiple Stored Cross Site Scripting (XSS) vulnerabilities in Opart opartmultihtmlblock before version 2.0.12 and Opart multihtmlblock* version 1.0.0, allows remote authenticated users to inject arbitrary web script or HTML via the body_text or body_text_rude field in /sourcefiles/BlockhtmlClass.php and /sourcefiles/blockhtml.php.

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

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

It affects 1 product.


Products: Store-Opart Multi Html Block.

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

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

## Is CVE-2023-30148 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-30148 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 Oct 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-30148 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-30148/ (Markdown: https://insights.sbomify.com/CVE-2023-30148/index.md)
```

## Sources

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

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