CVE-2021-29050
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in the terms of use page in Liferay Portal before 7.3.6, and Liferay DXP 7.3 before service pack 1, 7.2 before fix pack 11 allows remote attackers to accept the site's terms of use via social engineering and enticing the user to visit a malicious page.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA CSRF vulnerability in LPortal and Lifer DXP's terms of use acceptance functionality allows authenticated users to unknowingly accept terms of use via a maliciously crafted request triggered from an attacker's page. The attack exploits the lack of anti-CSRF token validation on the terms of use acceptance endpoint.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify LPortal or Lifer DXP installation versionCheck the product's version information through the control panel (typically under Control Panel > Configuration > Server Information) or by locating the version file in the installation directoryAffected if The installed version is before 7.3.6 for LPortal, or before 7.3 SP1 / 7.2 FP11 for DXP
-
Verify terms of use acceptance feature is enabledNavigate to Control Panel > Configuration > Portal Settings > Terms of Use and confirm if the feature is enabled for usersAffected if Terms of use acceptance is required/enabled for user accounts in the environment
-
Inspect the terms of use acceptance form for anti-CSRF protectionAccess the terms of use acceptance page, view the HTML source, and check if a CSRF token or security token field is present in the form submissionAffected if The form lacks a CSRF token parameter or anti-CSRF validation mechanism
Users are affected if their LPortal version is below 7.3.6 or DXP is below 7.3 SP1/7.2 FP11 AND the terms of use acceptance feature is enabled, since the endpoint lacks anti-CSRF token validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the vendor patches (LPortal 7.3.6+, DXP 7.3 SP1+, or 7.2 FP11+) which add anti-CSRF token validation to the terms of use acceptance form.
Liferay Portal 7.3.6+ | Liferay DXP 7.3 Service Pack 1+ | Liferay DXP 7.2 Fix Pack 11+
- 1. Identify the current Liferay product (Portal or DXP) and exact version running in your environment
- 2. For Liferay Portal: Upgrade to version 7.3.6 or later
- 3. For Liferay DXP 7.3: Apply Service Pack 1 or later
- 4. For Liferay DXP 7.2: Apply Fix Pack 11 or later
- 5. After upgrade, verify the terms of use functionality works correctly and test for any regressions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-29050 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-29050 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data