Skip to content
Fencer Intel
medium 5.3

CVE-2024-26267 json

Liferay Portal and Liferay DXP HTTP Header Can Expose Versions

published 2y ago modified 4mo ago also GHSA-2mvj-q2q3-wxjv , EUVD-2024-23541

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

In Liferay Portal 7.2.0 through 7.4.3.25, and older unsupported versions, and Liferay DXP 7.4 before update 26, 7.3 before update 5, 7.2 before fix pack 19, and older unsupported versions the default value of the portal property `http.header.version.verbosity` is set to `full`, which allows remote attackers to easily identify the version of the application that is running and the vulnerabilities that affect that version via 'Liferay-Portal` response header.

Patch / fix

  • maven com.liferay.portal:release.portal.bom 7.4.3.26-ga26
  • maven com.liferay.portal:release.dxp.bom 7.2.10.fp19, 7.3.10.u5, 7.4.13.u26
  • liferay liferay_portal 7.4.3.26
  • liferay digital_experience_platform 7.2

Is CVE-2024-26267 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
no
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.26-ga26
7.4.3.26-ga26
maven com.liferay.portal:release.dxp.bom
<7.2.10.fp19
>=7.3.0, <7.3.10.u5
>=7.4.0, <7.4.13.u26
7.2.10.fp19
7.3.10.u5
7.4.13.u26

Affected products

  • Liferay Portal
  • Liferay DXP

Classification

Weakness
  • CWE-1188 Initialization of a Resource with an Insecure Default

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.