# CVE-2024-34697: Freescout vulnerable to Stored HTML Injection in Editing Received Emails > Unauthenticated attackers can inject malicious HTML into received emails, enabling data exfiltration or defacement in FreeScout help desk. - **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L`) - **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:** No - **Published:** 13 May 2024 - **Updated:** 2 Aug 2024 - **Also known as:** GHSA-985r-6qfc-hg8m ## What is CVE-2024-34697? CVE-2024-34697 is a high-severity cross-site scripting vulnerability in freescout-helpdesk freescout, published on 13 May 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 FreeScout is a free, self-hosted help desk and shared mailbox. A stored HTML Injection vulnerability has been identified in the Email Receival Module of the Freescout Application. The vulnerability allows attackers to inject malicious HTML content into emails sent to the application's mailbox. This vulnerability arises from improper handling of HTML content within incoming emails, allowing attackers to embed malicious HTML code in the context of the application's domain. Unauthenticated attackers can exploit this vulnerability to inject malicious HTML content into emails. This could lead to various attacks such as form hijacking, application defacement, or data exfiltration via CSS injection. Although unauthenticated attackers are limited to HTML injection, the consequences can still be severe. Version 1.8.139 implements strict input validation and sanitization mechanisms to ensure that any HTML content received via emails is properly sanitized to prevent malicious HTML injections. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component) ## Which versions are affected by CVE-2024-34697? It affects 1 product. Products: Freescout Freescout. ## How do I fix CVE-2024-34697? No fix has been published for CVE-2024-34697 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-34697 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-34697 exists. ## Other vulnerabilities in freescout-helpdesk freescout - [CVE-2026-28289](https://insights.sbomify.com/CVE-2026-28289/): FreeScout 1.8.206 Patch Bypass for CVE-2026-27636 via Zero-Width Space Character Leads to Remote Code Execution (critical 10.0) - [CVE-2026-27637](https://insights.sbomify.com/CVE-2026-27637/): FreeScout's Predictable Authentication Token Enables Account Takeover (critical 9.8) - [CVE-2026-32754](https://insights.sbomify.com/CVE-2026-32754/): FreeScout: Stored XSS via Unescaped Email Template Rendering ({!! $thread->body !!}) (critical 9.3) - [CVE-2024-29185](https://insights.sbomify.com/CVE-2024-29185/): FreeScout OS Command Injection vulnerability (critical 9.1) - [CVE-2026-40498](https://insights.sbomify.com/CVE-2026-40498/): FreeScout has Authentication Bypass and Information Disclosure in SystemController via /system/cron (high 8.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-34697 and fix it if it is affected. What it is: CVE-2024-34697 is a high-severity cross-site scripting vulnerability in freescout-helpdesk freescout, published on 13 May 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-34697 exists. Affected product: freescout-helpdesk freescout. 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-2024-34697/ (Markdown: https://insights.sbomify.com/CVE-2024-34697/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-34697 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-34697 - OSV: https://osv.dev/vulnerability/CVE-2024-34697 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-34697/ Summaries are generated and may contain mistakes; the official description above is the record.