# CVE-2024-32464: ActionText ContentAttachment can Contain Unsanitized HTML

> Attackers can inject unsanitized HTML into ActionText attachments, potentially leading to cross-site scripting attacks in Rails applications.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** BIT-rails-2024-32464, GHSA-prjp-h48f-jgf6, UBUNTU-CVE-2024-32464

## What is CVE-2024-32464?

CVE-2024-32464 is a medium-severity cross-site scripting vulnerability in Rubyonrails Rails, published on 4 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Action Text brings rich text content and editing to Rails. Instances of ActionText::Attachable::ContentAttachment included within a rich_text_area tag could potentially contain unsanitized HTML. This vulnerability is fixed in 7.1.3.4 and 7.2.0.beta2.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

5 open source packages ship an affected version, including rails and actiontext. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rails` | Bitnami | From 7.1.0 | 7.1.4 |
| `actiontext` | RubyGems | From 7.1.0 | 7.1.3.4 |
| `actiontext` | RubyGems | From 7.1.0 | 7.1.3.4 |
| `actiontext` | RubyGems | From 7.2.0.beta1 | 7.2.0.beta2 |
| `actiontext` | RubyGems | From 7.2.0.beta1 | 7.2.0.beta2 |

Products: Rubyonrails Rails.

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

Upgrade rails to 7.1.4 or later.

## Is CVE-2024-32464 being exploited?

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

## Other vulnerabilities in Rubyonrails Rails

- [CVE-2013-0277](https://insights.sbomify.com/CVE-2013-0277/): Active Record contains deserialization of arbitrary YAML (critical 10.0)
- [CVE-2017-17916](https://insights.sbomify.com/CVE-2017-17916/): SQL injection in n/a (high 8.1)
- [CVE-2017-17917](https://insights.sbomify.com/CVE-2017-17917/): SQL injection in n/a (high 8.1)
- [CVE-2026-33195](https://insights.sbomify.com/CVE-2026-33195/): Rails Active Storage has possible Path Traversal in DiskService (high 8.0)
- [CVE-2024-26142](https://insights.sbomify.com/CVE-2024-26142/): Rails possible ReDoS vulnerability in Accept header parsing in Action Dispatch (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-32464 is a medium-severity cross-site scripting vulnerability in Rubyonrails Rails, published on 4 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-32464 in the wild and no public exploit code.

Affected packages and fixed versions:
- rails (Bitnami): affected from 7.1.0; fixed in 7.1.4
- actiontext (RubyGems): affected from 7.1.0; fixed in 7.1.3.4
- actiontext (RubyGems): affected from 7.1.0; fixed in 7.1.3.4
- actiontext (RubyGems): affected from 7.2.0.beta1; fixed in 7.2.0.beta2
- actiontext (RubyGems): affected from 7.2.0.beta1; fixed in 7.2.0.beta2

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

## Sources

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

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