Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-68927: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in abhinavxd libredesk

0
High
VulnerabilityCVE-2025-68927cvecve-2025-68927cwe-79
Published: Sat Dec 27 2025 (12/27/2025, 00:04:49 UTC)
Source: CVE Database V5
Vendor/Project: abhinavxd
Product: libredesk

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.

AI-Powered Analysis

AILast updated: 01/03/2026, 22:57:28 UTC

Technical Analysis

CVE-2025-68927 is a stored cross-site scripting vulnerability affecting LibreDesk, a self-hosted customer support desk software. The vulnerability arises in the contact notes feature where user input submitted via the POST /api/v1/contacts/{id}/notes endpoint is automatically wrapped in <p> tags by the backend. However, attackers can intercept and modify the request to remove these <p> tags, enabling injection of arbitrary HTML elements such as forms, images, or scripts. Because the input is stored and later rendered without proper sanitization or encoding, malicious payloads persist and execute in the context of users viewing the notes. This can facilitate phishing attacks by displaying deceptive forms, CSRF-style forced actions by tricking users into submitting unintended requests, and UI redress attacks that manipulate the user interface to mislead users. The vulnerability does not require authentication to exploit but does require user interaction to trigger the payload. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges required, user interaction required, and high impact on confidentiality and integrity. The vulnerability was publicly disclosed on December 27, 2025, and patched in LibreDesk version 0.8.6-beta. No known exploits have been reported in the wild as of now.

Potential Impact

For European organizations using LibreDesk versions prior to 0.8.6-beta, this vulnerability poses significant risks. As LibreDesk is used for customer support, exploitation could lead to compromise of sensitive customer data confidentiality and integrity through phishing or forced actions. Attackers could manipulate support agents or customers into performing unintended operations, potentially leading to data leakage, unauthorized changes, or reputational damage. The stored nature of the XSS means malicious payloads persist and can affect multiple users over time. This is particularly impactful for organizations handling sensitive or regulated customer information under GDPR, where data breaches can result in heavy fines and legal consequences. Additionally, the ability to conduct CSRF-style attacks could allow attackers to escalate their impact beyond just UI manipulation. The lack of required authentication lowers the barrier for attackers, increasing the threat surface. Although no exploits are currently known in the wild, the high CVSS score and ease of exploitation warrant immediate attention.

Mitigation Recommendations

European organizations should immediately upgrade LibreDesk to version 0.8.6-beta or later to apply the official patch that properly sanitizes and encodes user input in contact notes. Until upgrading is possible, organizations should implement strict input validation and output encoding on the contact notes feature to prevent HTML injection. Web application firewalls (WAFs) can be configured to detect and block suspicious payloads targeting the notes endpoint. Monitoring and alerting on unusual POST requests to /api/v1/contacts/{id}/notes can help detect exploitation attempts. User education for support staff to recognize phishing and UI redress attacks is also critical. Additionally, organizations should review access controls and audit logs for any suspicious activity related to contact notes. Regular security assessments and penetration testing focused on the customer support platform will help identify residual risks. Finally, organizations should ensure incident response plans include scenarios involving XSS exploitation in customer-facing applications.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-12-24T23:40:31.797Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 694f5b38b11716a1460d26a0

Added to database: 12/27/2025, 4:06:16 AM

Last enriched: 1/3/2026, 10:57:28 PM

Last updated: 2/7/2026, 1:08:26 AM

Views: 46

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats