NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2021-33320 — com.liferay.flags.taglib

MEDIUM

CVE-2021-33320 is a medium-severity (CVSS 4.3) CWE-770 vulnerability in com.liferay:com.liferay.flags.taglib. A fix is available for com.liferay:com.liferay.flags.taglib — see the affected versions and patch details below.

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

Also known asGHSA-wg4x-hf94-fj5v
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs67th percentile — riskier than 67% of all scored CVEsHighest risk
0.00%0.56%1.13%1.70%0.4%1.2%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected
☕com.liferay:com.liferay.flags.taglib☕com.liferay.portal:release.dxp.bom☕com.liferay.portal:release.dxp.bom☕com.liferay.portal:release.dxp.bom

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

The Flags module before version 5.0.11 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

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
☕Mavencom.liferay:com.liferay.flags.tagliball versions5.0.11com.liferay:com.liferay.flags.taglib:5.0.11
☕Mavencom.liferay.portal:release.dxp.bom≥ 7.0.0&&< 7.0.10.fp967.0.10.fp96com.liferay.portal:release.dxp.bom:7.0.10.fp96
☕Mavencom.liferay.portal:release.dxp.bom≥ 7.1.0&&< 7.1.10.fp207.1.10.fp20com.liferay.portal:release.dxp.bom:7.1.10.fp20
☕Mavencom.liferay.portal:release.dxp.bom≥ 7.2.0&&< 7.2.10.fp57.2.10.fp5com.liferay.portal:release.dxp.bom:7.2.10.fp5

Affected Products

2 products · 91 configurations
Application
digital experience platformliferay
3 versions
7.07.17.2
Application
liferay portalliferay
< 7.3.1
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay:com.liferay.flags.taglib, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update com.liferay:com.liferay.flags.taglib to 5.0.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-33320 is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

The Flags module before version 5.0.11 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
O3 Security · Impact-Aware SCA

Is CVE-2021-33320 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2021-33320: com.liferay.flags.taglib — Fixed in 5.0.11