# CVE-2024-22411: Cross site scripting in Action messages on Avo

> Attackers can inject malicious scripts via unsanitized action messages in Avo admin panels, potentially compromising user sessions.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L`)
- **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:** 2 Jun 2025
- **Also known as:** GHSA-g8vp-2v5p-9qfh

## What is CVE-2024-22411?

CVE-2024-22411 is a medium-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. In Avo 3 pre12, any HTML inside text that is passed to `error` or `succeed` in an `Avo::BaseAction` subclass will be rendered directly without sanitization in the toast/notification that appears in the UI on Action completion. A malicious user could exploit this vulnerability to trigger a cross site scripting attack on an unsuspecting user. This issue has been addressed in the 3.3.0 and 2.47.0 releases of Avo. Users are advised to upgrade.

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

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

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.3.0 |
| `avo` | RubyGems | From 3.0.0.beta1 | 3.3.0 |

Products: Avohq Avo.

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

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

## Is CVE-2024-22411 being exploited?

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

Public exploit code:

- https://github.com/tamaloa/avo-CVE-2024-22411 (github_poc): https://github.com/tamaloa/avo-CVE-2024-22411

## 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-2024-22191](https://insights.sbomify.com/CVE-2024-22191/): Stored cross-site scripting (XSS) in `key_value` field in Avo (high 7.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-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-22411 and fix it if it is affected.

What it is: CVE-2024-22411 is a medium-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-22411 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.3.0
- avo (RubyGems): affected from 3.0.0.beta1; fixed in 3.3.0

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

## Sources

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

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