Skip to content
Fencer Intel
medium 6.1

CVE-2022-26596 json

Liferay Portal and Liferay DXP allows arbitrary injection via web content template names

published 4y ago modified 4mo ago also BIT-liferay-2022-26596 , EUVD-2022-31151 , GHSA-w7f2-6896-6mm2

cvss
6.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits
0
none known

Summary

Cross-site scripting (XSS) vulnerability in Journal module's web content display configuration page in Liferay Portal 7.1.0 through 7.3.3, and Liferay DXP 7.0 before fix pack 94, 7.1 before fix pack 19, and 7.2 before fix pack 8, allows remote attackers to inject arbitrary web script or HTML via web content template names.

Patch / fix

  • maven com.liferay:com.liferay.journal.content.web 5.0.15
  • maven com.liferay.portal:release.dxp.bom 7.0.10.fp94, 7.1.10.fp19, 7.2.10.fp8

Is CVE-2022-26596 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

Exploit prediction

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

CVSS scores

assigned by version score vector
GitHub 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N
OSV 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven com.liferay:com.liferay.journal.content.web
<5.0.15
5.0.15
maven com.liferay.portal:release.dxp.bom
>=7.0.0, <7.0.10.fp94
>=7.1.0, <7.1.10.fp19
>=7.2.0, <7.2.10.fp8
7.0.10.fp94
7.1.10.fp19
7.2.10.fp8
bitnami liferay
>=7.0.0, <=7.0.0
>=7.1.0, <=7.1.0
>=7.2.0, <=7.2.0
>=7.0-fix.0, <=7.0-fix.0
>=7.1-fix.0, <=7.1-fix.0
>=7.2-fix.0, <=7.2-fix.0
no fix listed

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.