# CVE-2024-22191: Stored cross-site scripting (XSS) in `key_value` field in Avo

> Stored XSS in Avo's key_value field allows attackers to execute arbitrary JavaScript, potentially stealing data or hijacking accounts.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/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:** Yes
- **Published:** 16 Jan 2024
- **Updated:** 21 Oct 2024
- **Also known as:** GHSA-ghjv-mh6x-7q6h

## What is CVE-2024-22191?

CVE-2024-22191 is a high-severity cross-site scripting vulnerability in avo-hq avo, published on 16 Jan 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Avo is a framework to create admin panels for Ruby on Rails apps. A stored cross-site scripting (XSS) vulnerability was found in the key_value field of Avo v3.2.3 and v2.46.0. This vulnerability could allow an attacker to execute arbitrary JavaScript code in the victim's browser. The value of the key_value is inserted directly into the HTML code. In the current version of Avo (possibly also older versions), the value is not properly sanitized before it is inserted into the HTML code. This vulnerability could be used to steal sensitive information from victims that could be used to hijack victims' accounts or redirect them to malicious websites. Avo 3.2.4 and 2.47.0 include a fix for this issue. Users are advised to upgrade.

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

## Which versions are affected by CVE-2024-22191?

4 open source packages ship an affected version, including avo. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `avo` | RubyGems | All versions | 2.47.0 |
| `avo` | RubyGems | All versions | 2.47.0 |
| `avo` | RubyGems | From 3.0.0.beta1 | 3.2.4 |
| `avo` | RubyGems | From 3.0.0.beta1 | 3.2.4 |

Products: Avohq Avo.

## How do I fix CVE-2024-22191?

Upgrade avo to a fixed version for your release line: 2.47.0 or 3.2.4.

## Is CVE-2024-22191 being exploited?

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

## Other vulnerabilities in avo-hq avo

- [CVE-2023-34102](https://insights.sbomify.com/CVE-2023-34102/): Possible unsafe reflection / partial denial of service in avo (high 8.3)
- [CVE-2023-34103](https://insights.sbomify.com/CVE-2023-34103/): Stored XSS (Cross Site Scripting) in html content based fields of avo (high 7.3)
- [CVE-2024-22411](https://insights.sbomify.com/CVE-2024-22411/): Cross site scripting in Action messages on Avo (medium 6.5)
- [CVE-2026-33209](https://insights.sbomify.com/CVE-2026-33209/): Avo has a XSS vulnerability on `return_to` param (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22191 and fix it if it is affected.

What it is: CVE-2024-22191 is a high-severity cross-site scripting vulnerability in avo-hq avo, published on 16 Jan 2024. 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-2024-22191 exists.

Affected packages and fixed versions:
- avo (RubyGems): affected all versions; fixed in 2.47.0
- avo (RubyGems): affected all versions; fixed in 2.47.0
- avo (RubyGems): affected from 3.0.0.beta1; fixed in 3.2.4
- avo (RubyGems): affected from 3.0.0.beta1; fixed in 3.2.4

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

## Sources

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

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