Liferay Portal and Liferay DXP Vulnerable to XSS via the OAuth2ProviderApplicationRedirect Class

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

EPSS

• CVE-2023-44311: 0.57% estimated exploitation activity in the next 30 days; percentile 47.09 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Multiple reflected cross-site scripting (XSS) vulnerabilities in the Plugin for OAuth 2.0 module's OAuth2ProviderApplicationRedirect class before 4.0.51 from Liferay Portal (7.4.3.41 through 7.4.3.89), and Liferay DXP 7.4 update 41 through update 89 allow remote attackers to inject arbitrary web script or HTML via the (1) code, or (2) error parameter. This issue is caused by an incomplete fix in CVE-2023-33941.

Published by the source

17 Oct 2023, 12:30 UTC

Last modified by the source

15 Jul 2025, 20:18 UTC

Source last checked

26 Oct 2026, 16:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-49gm-5685-8fxv

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

# Patch Next advisory brief: CVE-2023-44311

Advisory: Liferay Portal and Liferay DXP Vulnerable to XSS via the OAuth2ProviderApplicationRedirect Class
IDs: CVE-2023-44311, GHSA-49gm-5685-8fxv
Record: https://patchnext.com/advisories/cve-2023-44311 (revision 1, source checked 26 Oct 2026, 16:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.liferay.portal:release.dxp.bom 7.4.13.u90; com.liferay:com.liferay.oauth2.provider.rest 4.0.51. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.liferay.portal:release.dxp.bom: affected >= 7.4.13.u41, < 7.4.13.u90; fixed in 7.4.13.u90
- Maven com.liferay:com.liferay.oauth2.provider.rest: affected < 4.0.51; fixed in 4.0.51

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.liferay.portal:release.dxp.bom, com.liferay:com.liferay.oauth2.provider.rest.
- 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-49gm-5685-8fxv (GitHub-reviewed advisory GHSA-49gm-5685-8fxv lists affected ranges: Maven com.liferay:com.liferay.oauth2.provider.rest >=0 =7.4.13.u41 <7.4.13.u90)

Commands are suggestions: review each one before running it.