CVE-2025-12546VulnerabilityPublished 31 Oct 2025

CVE-2025-12546: LogicalDOC Community Edition · Cross Site Scripting

Affects LogicalDOC Community EditionSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
LogicalDOC Community Edition	Affected =9.2.0 =9.2.1	Fixed in–

AI-suggested

European organizations should immediately review their use of LogicalDOC Community Edition versions 9.2.0 and 9.2.1 and consider the following specific mitigations: 1) Restrict access to the API Key creation UI to trusted administrators only, using network segmentation and access control lists to limit exposure. 2) Implement web application firewalls (WAFs) with custom rules to detect and block XSS payloads targeting LogicalDOC interfaces. 3) Educate users about the risks of clicking untrusted links or interacting with suspicious content related to LogicalDOC. 4) Monitor application logs for unusual activity around API key creation or user sessions to detect potential exploitation attempts. 5) If feasible, migrate to a newer or alternative document management solution that is actively maintained and patched. 6) Employ Content Security Policy (CSP) headers to reduce the impact of XSS by restricting script execution sources. 7) Regularly backup LogicalDOC data and configurations to enable recovery in case of compromise. 8) Engage with the LogicalDOC community or security forums to track any unofficial patches or mitigations until an official fix is released.

Description

A vulnerability was determined in LogicalDOC Community Edition up to 9.2.1. This affects an unknown part of the component API Key creation UI. This manipulation causes cross site scripting. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, exploitation of this XSS vulnerability could lead to unauthorized access to user sessions, enabling attackers to perform actions on behalf of legitimate users or steal sensitive information accessible through the LogicalDOC interface. This could compromise document confidentiality and integrity, especially if API keys or administrative functions are targeted. While the vulnerability does not directly impact system availability, successful exploitation could facilitate further attacks or lateral movement within networks. Organizations handling sensitive or regulated documents (e.g., legal, financial, healthcare sectors) face increased risks of data breaches or compliance violations. The lack of vendor response and patches prolongs exposure, increasing the window for attackers to develop and deploy exploits. Given LogicalDOC’s use in collaborative and document-intensive environments, the impact could extend to multiple users and departments within affected organizations.

Summary

CVE-2025-12546 identifies a cross-site scripting vulnerability in LogicalDOC Community Edition, specifically affecting versions 9.2.0 and 9.2.1. The vulnerability resides in the API Key creation UI component, where insufficient input sanitization allows attackers to inject malicious JavaScript code. This flaw enables remote attackers to execute scripts in the context of the victim’s browser, potentially leading to session hijacking, defacement, or unauthorized actions within the application. The attack vector requires no authentication but does require user interaction, such as clicking a crafted link or visiting a malicious page. The CVSS 4.0 score of 5.1 reflects a medium severity, considering the ease of exploitation (low complexity), lack of required privileges, but limited impact on confidentiality and integrity. The vendor was notified early but has not issued patches or responses, leaving users exposed. Although no active exploits have been reported, the public disclosure increases the likelihood of exploitation attempts. LogicalDOC Community Edition is an open-source document management system used by various organizations for managing digital documents, making this vulnerability relevant for environments relying on this software for secure document workflows.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 31 Oct 2025, 18:50 UTC

Technical details

References

Community reviews

Related threats