Skip to content
Fencer Intel
medium 4.8

CVE-2023-37940 json

Liferay Portal and Liferay DXP have Cross-site Scripting vulnerability in edit Service Access Policy page

published last yr. modified 4mo ago also GHSA-px38-239g-x5mg , EUVD-2024-3606

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

Summary

Cross-site scripting (XSS) vulnerability in the edit Service Access Policy page in Liferay Portal 7.0.0 through 7.4.3.87, and Liferay DXP 7.4 GA through update 87, 7.3 GA through update 29, and older unsupported versions allows remote attackers to inject arbitrary web script or HTML via a crafted payload injected into a service access policy's `Service Class` text field.

Patch / fix

  • maven com.liferay.portal:release.portal.bom 7.4.3.88
  • maven com.liferay.portal:release.dxp.bom 7.3.10.u30, 7.4.13.u88
  • liferay liferay_portal 7.4.3.88
  • liferay digital_experience_platform 7.3

Is CVE-2023-37940 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
last yr.

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven com.liferay.portal:release.portal.bom
>=7.0.0, <7.4.3.88
7.4.3.88
maven com.liferay.portal:release.dxp.bom
>=7.0, <7.3.10.u30
>=7.4, <7.4.13.u88
7.3.10.u30
7.4.13.u88

Affected products

  • Liferay Portal
  • Liferay DXP

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

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.