Skip to content
Fencer Intel
low 2.7

CVE-2023-33947 json

Liferay portal has unauthorized access to object definition via search

published 3y ago modified 4mo ago also BIT-liferay-2023-33947 , EUVD-2023-1490 , GHSA-769c-p92r-xgxj

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

Summary

The Object module in Liferay Portal 7.4.3.4 through 7.4.3.60, and Liferay DXP 7.4 before update 61 does not segment object definition by virtual instance in search which allows remote authenticated users in one virtual instance to view object definition from a second virtual instance by searching for the object definition.

Patch / fix

  • maven com.liferay.portal:release.portal.bom 7.4.3.61

Is CVE-2023-33947 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.61% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
CNA 3.1 2.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
OSV 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/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.4.3.4, <7.4.3.61
7.4.3.61
bitnami liferay
>=7.4.0, <=7.4.0
>=7.4-update1.0, <=7.4-update1.0
>=7.4-update21.0, <=7.4-update21.0
>=7.4-update34.0, <=7.4-update34.0
>=7.4-update36.0, <=7.4-update36.0
>=7.4-update41.0, <=7.4-update41.0
>=7.4-update50.0, <=7.4-update50.0
>=7.4-update52.0, <=7.4-update52.0
no fix listed

Affected products

  • Liferay Portal
  • Liferay DXP

Classification

Weakness

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.