Skip to main content
VulnerabilityPublished

CVE-2025-43754: Liferay Portal · Timing Side Channel

Affects Liferay PortalSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 17:16 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

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

What to do

Affected software

ProductAffectedFixed in
Liferay PortalAffected
  • =7.4.0
Fixed in–

AI-suggested

To mitigate this vulnerability, organizations should implement the following specific measures: 1) Apply any official patches or updates from Liferay as soon as they become available, as these will address the timing discrepancy at the application level. 2) Implement uniform response times for login attempts regardless of username validity to eliminate timing side channels. This can be done by introducing artificial delays or standardizing backend processing paths. 3) Employ account lockout or throttling mechanisms to limit the rate of login attempts, reducing the feasibility of automated enumeration. 4) Monitor authentication logs for unusual patterns indicative of enumeration attempts, such as high volumes of login requests with varying usernames from single IP addresses. 5) Use multi-factor authentication (MFA) to reduce the risk of account compromise even if usernames are known. 6) Consider deploying web application firewalls (WAFs) with rules designed to detect and block timing-based enumeration attacks. 7) Educate users and administrators about the risks of username enumeration and encourage strong, unique passwords to mitigate downstream risks. These mitigations go beyond generic advice by focusing on eliminating timing discrepancies and detecting enumeration behavior specifically in the context of Liferay Portal environments.

Description

Username enumeration vulnerability in Liferay Portal 7.4.0 through 7.4.3.132, and Liferay DXP 2024.Q4.0 through 2024.Q4.7, 2024.Q3.0 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.14 and 7.4 GA through update 92 allows attackers to determine if an account exist in the application by inspecting the server processing time of the login request.

References

Community reviews

Loading reviews…