Skip to content

← Actionable
Medium, CVSS 6.5

Liferay Portal and Liferay DXP vulnerable to theft of hashed password

CVE-2024-26270GHSA-xq4r-4xfh-vch8

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2024-26270: 0.44% estimated exploitation activity in the next 30 days; percentile 38.41 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

The Account Settings page in Liferay Portal 7.4.3.76 through 7.4.3.99, and Liferay DXP 2023.Q3 before patch 5, and 7.4 update 76 through 92 embeds the user’s hashed password in the page’s HTML source, which allows man-in-the-middle attackers to steal a user's hashed password.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-xq4r-4xfh-vch8

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-26270

Advisory: Liferay Portal and Liferay DXP vulnerable to theft of hashed password
IDs: CVE-2024-26270, GHSA-xq4r-4xfh-vch8
Record: https://patchnext.com/advisories/cve-2024-26270 (revision 1, source checked 26 Oct 2026, 16:44 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: com.liferay.portal:release.portal.bom 7.4.3.100; com.liferay.portal:release.dxp.bom 2023.Q3.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.liferay.portal:release.portal.bom: affected >= 7.4.3.76, < 7.4.3.100; fixed in 7.4.3.100
- Maven com.liferay.portal:release.dxp.bom: affected >= 2023.Q3, < 2023.Q3.5; >= 7.4.0, <= 7.4.13.u92; fixed in 2023.Q3.5

## Suggested inspection (read-only)
- Maven com.liferay.portal:release.portal.bom: check the installed version with your package manager.
- Maven com.liferay.portal:release.dxp.bom: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.liferay.portal:release.portal.bom, com.liferay.portal:release.dxp.bom.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xq4r-4xfh-vch8 (GitHub-reviewed advisory GHSA-xq4r-4xfh-vch8 lists affected ranges: Maven com.liferay.portal:release.portal.bom >=7.4.3.76 =2023.Q3 =7.4.0 <=7.4.13.u92)

Commands are suggestions: review each one before running it.

Loading voting…