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-11946: Cross Site Scripting in LogicalDOC Community Edition

0
Medium
VulnerabilityCVE-2025-11946cvecve-2025-11946
Published: Sun Oct 19 2025 (10/19/2025, 21:32:06 UTC)
Source: CVE Database V5
Vendor/Project: LogicalDOC
Product: Community Edition

Description

A security flaw has been discovered in LogicalDOC Community Edition up to 9.2.1. This issue affects some unknown processing of the file /frontend.jsp of the component Add Contact Page. Performing manipulation of the argument First Name/Last Name/Company/Address/Phone/Mobile results in cross site scripting. Remote exploitation of the attack is possible. The exploit has been released to the public and may be exploited. The vendor was contacted early about this disclosure but did not respond in any way.

AI-Powered Analysis

AILast updated: 10/19/2025, 21:55:16 UTC

Technical Analysis

CVE-2025-11946 is a cross-site scripting (XSS) vulnerability identified in LogicalDOC Community Edition versions 9.2.0 and 9.2.1, specifically within the /frontend.jsp file of the Add Contact Page component. The vulnerability arises from improper sanitization and validation of user-supplied input fields including First Name, Last Name, Company, Address, Phone, and Mobile. An attacker can craft malicious input that, when processed by the vulnerable page, results in the execution of arbitrary JavaScript code in the context of the victim's browser. This can lead to session hijacking, theft of sensitive information, or execution of unauthorized actions on behalf of the user. The vulnerability is remotely exploitable without requiring authentication, though it does require user interaction to trigger the malicious payload. The vendor was notified early but has not issued a patch or response, and the exploit code has been publicly released, increasing the risk of exploitation. The CVSS 4.0 base score is 5.1, reflecting medium severity, with network attack vector, low attack complexity, no privileges required, but requiring user interaction. No known exploits in the wild have been reported yet. The lack of vendor response and patch availability necessitates immediate attention from users of affected versions. LogicalDOC is a document management system used for organizing and managing digital documents, and this vulnerability could compromise the confidentiality and integrity of stored information if exploited.

Potential Impact

For European organizations, exploitation of this XSS vulnerability could lead to unauthorized access to sensitive document management interfaces, theft of session cookies, and potential compromise of user accounts. This can result in data leakage, unauthorized document modification, or further lateral movement within the network. Since LogicalDOC is used to manage critical business documents, the integrity and confidentiality of corporate data could be at risk. The remote and unauthenticated nature of the exploit increases the attack surface, especially for organizations exposing LogicalDOC interfaces to the internet or large internal user bases. Public exploit availability raises the likelihood of opportunistic attacks, potentially targeting sectors with high document management needs such as legal, financial, and governmental institutions. The absence of vendor patches means organizations must rely on interim mitigations, increasing operational risk. Additionally, exploitation could undermine compliance with European data protection regulations like GDPR if personal or sensitive data is exposed.

Mitigation Recommendations

1. Immediately restrict external access to the LogicalDOC Community Edition interface, especially the /frontend.jsp Add Contact Page, using network segmentation or firewall rules. 2. Implement web application firewall (WAF) rules to detect and block malicious input patterns targeting the affected fields. 3. Apply strict input validation and output encoding on all user-supplied data fields (First Name, Last Name, Company, Address, Phone, Mobile) to neutralize potential XSS payloads. 4. Monitor application logs and user activity for unusual behavior indicative of XSS exploitation attempts. 5. Educate users to be cautious of suspicious links or inputs that could trigger XSS attacks. 6. Consider deploying browser security features such as Content Security Policy (CSP) to limit script execution. 7. Track vendor communications for any forthcoming patches or updates and plan for immediate application once available. 8. If feasible, upgrade to a non-vulnerable version or alternative document management solutions until a patch is released. 9. Conduct internal penetration testing to identify any additional exposure related to this vulnerability. 10. Maintain regular backups of critical documents to mitigate impact from potential compromise.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-10-19T03:03:39.869Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68f55abbd03e41f5d7ce2284

Added to database: 10/19/2025, 9:40:11 PM

Last enriched: 10/19/2025, 9:55:16 PM

Last updated: 10/20/2025, 11:52:18 AM

Views: 34

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats