Skip to content
Fencer Intel
medium 5.3

CVE-2024-26268 json

Liferay Portal and Liferay DXP User Enumeration Vulnerability

published 2y ago modified 4mo ago also GHSA-qm43-g2xj-hvg5 , EUVD-2024-23542

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 45%
public exploits
0
none known

Summary

User enumeration vulnerability in Liferay Portal 7.2.0 through 7.4.3.26, and older unsupported versions, and Liferay DXP 7.4 before update 27, 7.3 before update 8, 7.2 before fix pack 20, and older unsupported versions allows remote attackers to determine if an account exist in the application by comparing the request's response time.

Patch / fix

  • maven com.liferay.portal:release.portal.bom 7.4.3.27-ga27
  • maven com.liferay.portal:release.dxp.bom 7.2.10.fp20, 7.3.10.u8, 7.4.13.u27
  • liferay liferay_portal 7.4.3.27
  • liferay digital_experience_platform 7.2

Is CVE-2024-26268 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.53% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven com.liferay.portal:release.portal.bom
>=7.2.0, <7.4.3.27-ga27
7.4.3.27-ga27
maven com.liferay.portal:release.dxp.bom
<7.2.10.fp20
>=7.3.0, <7.3.10.u8
>=7.4.0, <7.4.13.u27
7.2.10.fp20
7.3.10.u8
7.4.13.u27

Affected products

  • Liferay Portal
  • Liferay DXP
  • liferay liferay_enterprise_portal
  • ibexa digital_experience_platform

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.