Skip to main content
VulnerabilityPublished

CVE-2025-12547: LogicalDOC Community Edition · Improper Restriction of Excessive Authentication Attempts

Affects LogicalDOC Community EditionSource CVE Database V5

0

Public exploit available · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
LogicalDOC Community EditionAffected
  • =9.2.0
  • =9.2.1
Fixed in–

AI-suggested

Given the absence of an official patch, European organizations should implement specific mitigations: 1) Deploy Web Application Firewalls (WAFs) with rules to detect and block brute-force login attempts targeting /login.jsp. 2) Implement network-level rate limiting and IP blacklisting to restrict repeated login attempts from the same source. 3) Enforce strong password policies and consider multi-factor authentication (MFA) for administrator accounts if supported by LogicalDOC or via external authentication proxies. 4) Monitor login logs closely for unusual authentication patterns and failed login spikes. 5) Isolate LogicalDOC servers within segmented network zones to limit lateral movement if compromised. 6) Consider temporary disabling remote admin login access or restricting it to trusted IP addresses. 7) Regularly back up document repositories and configuration to enable recovery in case of compromise. 8) Stay alert for vendor updates or community patches and apply them promptly once available. 9) Educate administrators on recognizing phishing or social engineering attempts that could facilitate credential theft. These targeted measures go beyond generic advice and address the specific attack vector and environment.

Description

A vulnerability was identified in LogicalDOC Community Edition up to 9.2.1. This vulnerability affects unknown code of the file /login.jsp of the component Admin Login Page. Such manipulation leads to improper restriction of excessive authentication attempts. The attack can be executed remotely. This attack is characterized by high complexity. It is stated that the exploitability is difficult. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

References

Community reviews

Loading reviews…