# CVE-2025-68927: Improper Neutralization of HTML Tags in a Web Page in libredesk

> Attackers can inject arbitrary HTML into contact notes, enabling phishing and UI redress attacks in LibreDesk.

- **Severity:** High 7.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P`)
- **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:** 27 Dec 2025
- **Updated:** 29 Dec 2025
- **Also known as:** GHSA-wh6m-h6f4-rjf4, GO-2025-4243

## What is CVE-2025-68927?

CVE-2025-68927 is a high-severity cross-site scripting vulnerability in abhinavxd libredesk, published on 27 Dec 2025. 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

Libredesk is a self-hosted customer support desk. Prior to version 0.8.6-beta, LibreDesk is vulnerable to stored HTML injection in the contact notes feature. When adding notes via POST /api/v1/contacts/{id}/notes, the backend automatically wraps user input in <p> tags. However, by intercepting the request and removing the <p> tag, an attacker can inject arbitrary HTML elements such as forms and images, which are then stored and rendered without proper sanitization. This can lead to phishing, CSRF-style forced actions, and UI redress attacks. This issue has been patched in version 0.8.6-beta.

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

## Which versions are affected by CVE-2025-68927?

3 open source packages ship an affected version, including github.com/abhinavxd/libredesk. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/abhinavxd/libredesk` | Go | All versions | None |
| `github.com/abhinavxd/libredesk` | Go | All versions | 0.8.6-beta |
| `github.com/abhinavxd/libredesk` | Go | All versions | 0.8.6-beta |

Products: Libredesk Libredesk.

## How do I fix CVE-2025-68927?

Upgrade github.com/abhinavxd/libredesk to 0.8.6-beta or later.

## Is CVE-2025-68927 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68927 and fix it if it is affected.

What it is: CVE-2025-68927 is a high-severity cross-site scripting vulnerability in abhinavxd libredesk, published on 27 Dec 2025. 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-2025-68927 exists.

Affected packages and fixed versions:
- github.com/abhinavxd/libredesk (Go): affected all versions; no fix listed
- github.com/abhinavxd/libredesk (Go): affected all versions; fixed in 0.8.6-beta
- github.com/abhinavxd/libredesk (Go): affected all versions; fixed in 0.8.6-beta

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

## Sources

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

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