Skip to content
Fencer Intel
medium 4.3

CVE-2021-33320 json

Liferay Portal and Liferay DXP vulnerable to email spam via lack of flagging rate

published 5y ago modified 4mo ago also GHSA-wg4x-hf94-fj5v , EUVD-2021-20029

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

Summary

The Flags module in Liferay Portal 7.3.1 and earlier, and Liferay DXP 7.0 before fix pack 96, 7.1 before fix pack 20, and 7.2 before fix pack 5, does not limit the rate at which content can be flagged as inappropriate, which allows remote authenticated users to spam the site administrator with emails

Patch / fix

  • maven com.liferay:com.liferay.flags.taglib 5.0.11
  • maven com.liferay.portal:release.dxp.bom 7.0.10.fp96, 7.1.10.fp20, 7.2.10.fp5
  • liferay liferay_portal 7.3.1

Is CVE-2021-33320 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

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven com.liferay:com.liferay.flags.taglib
<5.0.11
5.0.11
maven com.liferay.portal:release.dxp.bom
>=7.0.0, <7.0.10.fp96
>=7.1.0, <7.1.10.fp20
>=7.2.0, <7.2.10.fp5
7.0.10.fp96
7.1.10.fp20
7.2.10.fp5

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling

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.