# CVE-2022-26088: Cross-site scripting in n/a

> Remote authenticated users can inject HTML into the Activity Log via the To field, potentially enabling XSS or SSRF attacks.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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:** 10 Nov 2022
- **Updated:** 1 May 2025
- **Also known as:** GHSA-9545-r5rj-jc95

## What is CVE-2022-26088?

CVE-2022-26088 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 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

An issue was discovered in BMC Remedy before 22.1. Email-based Incident Forwarding allows remote authenticated users to inject HTML (such as an SSRF payload) into the Activity Log by placing it in the To: field. This affects rendering that occurs upon a click in the "number of recipients" field. NOTE: the vendor's position is that "no real impact is demonstrated."

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

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

It affects 1 product.


Products: Bmc Remedy It Service Management Suite.

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

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

## Is CVE-2022-26088 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-26088 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2022-26088 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-26088 exists.

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

## Sources

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

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