CVE-2021-29039
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 scripting (XSS) vulnerability in the Asset module's categories administration page in Liferay Portal 7.3.4 allows remote attackers to inject arbitrary web script or HTML via the site name.
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 confidenceStored cross-site scripting (XSS) vulnerability in Liferay Portal 7.3.4's Asset module categories administration page allows remote attackers to inject arbitrary web script or HTML through the site name parameter due to insufficient input sanitization and output encoding.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7.3.4CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Check Lifera Portal versionLog into the Lifera control panel and navigate to Control Panel > Configuration > Server Administration > Index, or check the version displayed in the footer of the Lifera welcome page. Alternatively, access the OSGi console and run the command to retrieve the portal version.Affected if The installed version is exactly 7.3.4 (Lifera Portal) as this is the only affected version for this CVE.
-
Verify Asset module categories administration accessNavigate to Control Panel > Content > Asset > Categories, or through the site administration panel if using Lifera DXP. Confirm you have administrative privileges to access this module.Affected if The Asset module categories administration functionality is present and accessible in the Lifera installation.
-
Locate the site name parameter in Asset categoriesIn the Asset categories administration interface, examine the category creation or editing form. Look for any site name field or association field that can be set when creating or managing asset categories.Affected if A site name or site association field exists within the Asset categories administration form where user-supplied input can be entered and stored.
-
Inspect stored category data for XSS payloadsUse the Lifera API or database query to retrieve stored asset category records. Examine the site name field in the stored data for any unsanitized HTML or script tags that may have been injected previously.Affected if The site name field in stored asset category records contains unsanitized HTML or JavaScript content that was not properly encoded upon storage or retrieval.
A user is affected if their Lifera Portal version is exactly 7.3.4 and they have used the Asset module categories administration functionality where the site name parameter accepts and stores unsanitized input that gets rendered without proper output encoding.
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.
From vendor dataApply Liferay security patches for CVE-2021-29039 and implement proper input validation and output encoding on the site name field in the Asset module's categories administration functionality.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-29039 — 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-29039 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