Libredesk has Improper Neutralization of HTML Tags in a Web Page

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

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 · score source

EPSS

• CVE-2025-68927: 0.23% estimated exploitation activity in the next 30 days; percentile 14.00 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. --- Details When notes are added through the LibreDesk web application, the client sends note content wrapped inside <p tags. The backend appears to trust this HTML structure and stores the content as-is. By intercepting the request to: and removing the <p wrapper, an attacker can submit arbitrary HTML content. The backend does not sanitize or validate the HTML payload before persisting it. As a result: Arbitrary HTML tags (e.g., <form, <input, <img) are stored The injected HTML is rendered when the notes are viewed…

Published by the source

16 Dec 2025, 20:43 UTC

Last modified by the source

31 Dec 2025, 00:13 UTC

Source last checked

26 Oct 2026, 15:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-wh6m-h6f4-rjf4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-68927

Advisory: Libredesk has Improper Neutralization of HTML Tags in a Web Page
IDs: CVE-2025-68927, GHSA-wh6m-h6f4-rjf4
Record: https://patchnext.com/advisories/cve-2025-68927 (revision 1, source checked 26 Oct 2026, 15:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/abhinavxd/libredesk 0.8.6-beta. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/abhinavxd/libredesk: affected < 0.8.6-beta; fixed in 0.8.6-beta

## Suggested inspection (read-only)
- Go github.com/abhinavxd/libredesk: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/abhinavxd/libredesk.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-wh6m-h6f4-rjf4 (GitHub-reviewed advisory GHSA-wh6m-h6f4-rjf4 lists affected ranges: Go github.com/abhinavxd/libredesk >=0 <0.8.6-beta)

Commands are suggestions: review each one before running it.