# CVE-2022-4892: MyCMS Visitors Module view.php build_view cross site scripting

> Remote attackers can inject malicious scripts via the Visitors Module, potentially compromising user sessions or data.

- **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:** 19 Jan 2023
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-8j86-xcpj-9xf9

## What is CVE-2022-4892?

CVE-2022-4892 is a low-severity cross-site scripting vulnerability in MyCMS, published on 19 Jan 2023. 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 MyCMS. It has been classified as problematic. This affects the function build_view of the file lib/gener/view.php of the component Visitors Module. The manipulation of the argument original/converted leads to cross site scripting. It is possible to initiate the attack remotely. The patch is named d64fcba4882a50e21cdbec3eb4a080cb694d26ee. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-218895.

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

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

It affects 1 product.


Products: Mycms Project Mycms.

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

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

## Is CVE-2022-4892 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4892 is a low-severity cross-site scripting vulnerability in MyCMS, published on 19 Jan 2023. 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-4892 in the wild and no public exploit code.

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

## Sources

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

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