CVE-2021-29045
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 Redirect module's redirection administration page in Liferay Portal 7.3.2 through 7.3.5, and Liferay DXP 7.3 before fix pack 1 allows remote attackers to inject arbitrary web script or HTML via the _com_liferay_redirect_web_internal_portlet_RedirectPortlet_destinationURL parameter.
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 stored Cross-Site Scripting (XSS) vulnerability exists in Liferays Redirect module administration page. The _com_libraries_redirect_web_internal_portlet_RedirectPortlet_destinationURL parameter does not properly sanitize user input before rendering, allowing authenticated administrators to inject arbitrary HTML or JavaScript that executes when the redirection administration page is viewed.
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>= 7.3.2, <= 7.3.5CVSS 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 your Liferay versionAccess the Liferay Control Panel, go to Configuration > Server Administration > Product Information, or inspect the portal-ext.properties file to find the exact version numberAffected if The version is Liferay DXP 7.3 (before fix pack 1) or Liferay Portal 7.3.2 through 7.3.5
-
Verify the Redirect module is installedIn the Liferay Control Panel, navigate to Apps > App Manager and search for 'Redirect' or check the osgi modules list for com_libraries_redirect_webAffected if The Redirect module is present and enabled in the system
-
Confirm access to Redirect administration pageNavigate to Control Panel > Configuration > Redirect or access the RedirectPortlet directly to verify the page is accessibleAffected if The Redirect administration interface is accessible to your user account
-
Check for stored XSS payloadsIf you have admin access, view the existing redirect configurations in the Redirect module and inspect the destinationURL field for any suspicious HTML or script tagsAffected if The destinationURL parameter accepts and stores unsanitized input containing HTML or JavaScript code
You are affected if your Liferay version falls within 7.3.2 to 7.3.5 (Portal) or is DXP 7.3, the Redirect module is enabled, and administrators can access the Redirect administration page where unsanitized input can be stored and rendered.
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 Liferays fix pack 1 for DXP 7.3, or upgrade to L Portal 7.3.6 or later. Until patched, restrict access to the Redirect module administration page to trusted administrators only.
- Consultation2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-29045 — 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-29045 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