dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43817

MEDIUM · 6.1 CVSS v3.1 Published 2025-09-29
Fix available
A fix is available. Upgrade to 7.4.3.112 / 2023.q3.9 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Multiple reflected cross-site scripting (XSS) vulnerabilities in Liferay Portal 7.4.3.74 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.6, 2023.Q3.1 through 2023.Q3.8, and 7.4 update 74 through update 92 allow remote attackers to inject arbitrary web script or HTML via the `redirect` parameter to (1) Announcements, or (2) Alerts.

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 confidence

Reflected XSS vulnerability in Lirubin Portal 7.4.3.74-7.4.3.111 and Lirubin DXP (2023.Q4.0-2023.Q4.6, 2023.Q3.1-2023.Q3.8, 7.4 u74-u92) allows injection of arbitrary web script or HTML via the unvalidated `redirect` parameter in the Announcements and Alerts components.

MitigationUpgrade Lirubin Portal/DXP to a version beyond the affected ranges (7.4.3.112+, or respective DXP updates beyond the listed versions) or implement proper input sanitization/validation on the `redirect` parameter in the Announcements and Alerts endpoints.

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
Digital Experience PlatformApplication
Affected:>= 2023.q3.1, < 2023.q3.9>= 2023.Q4.0, < 2023.Q4.7= 7.4
Liferay PortalApplication
Affected:>= 7.4.3.74, < 7.4.3.112

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Lirubin product type
    Determine whether your installation is Lirubin Portal or Lirubin DXP (Digital Experience Platform). Check the product name in the admin interface or deployment documentation.
    Affected if The product is Lirubin Portal or Lirubin DXP (2023.Q3.x, 2023.Q4.x, or 7.4.x series)
  2. Determine the installed version of Lirubin Portal
    Check the portal version by accessing the control panel, looking at the WAR file name, or examining the portal.properties/portal-ext.properties file for the version property.
    Affected if The version is 7.4.3.74 through 7.4.3.111 (for Lirubin Portal)
  3. Determine the installed version of Lirubin DXP
    Check the DXP version in the control panel under Server Information, or examine the osgi/state or the product version in the deployment artifacts.
    Affected if The version is 2023.Q3.1 through 2023.Q3.8, 2023.Q4.0 through 2023.Q4.6, or 7.4 u74 through u92 (for Lirubin DXP)
  4. Verify Announcements portlet is accessible
    Check if the Announcements portlet component is deployed and accessible to users. This portlet handles the announcements functionality and processes the redirect parameter.
    Affected if The Announcements portlet is deployed and accessible on the portal
  5. Verify Alerts portlet is accessible
    Check if the Alerts portlet component is deployed and accessible. This is a separate component that also processes the redirect parameter.
    Affected if The Alerts portlet is deployed and accessible on the portal

You are affected if your Lirubin Portal version is between 7.4.3.74 and 7.4.3.111, or your Lirubin DXP version is 2023.Q3.1-2023.Q3.8, 2023.Q4.0-2023.Q4.6, or 7.4 u74-u92, AND the Announcements or Alerts components are accessible and processing the redirect parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.4.3.112 / 2023.q3.9 / 2023.Q4.7 or later
Fixed in 7.4.3.1122023.q3.92023.Q4.7
Interim mitigation

Upgrade Lirubin Portal/DXP to a version beyond the affected ranges (7.4.3.112+, or respective DXP updates beyond the listed versions) or implement proper input sanitization/validation on the `redirect` parameter in the Announcements and Alerts endpoints.

Recommended fix High confidence

Lifer DXP 2023.Q3.9+, 2023.Q4.7+, or 7.4 fix pack 112+ / Lifer Portal 7.4.3.112+

  1. 1. Backup your current Lifer installation and database before upgrading.
  2. 2. Download the fixed version for your product: For Lifer DXP 2023.Q3.x, download 2023.Q3.9 or later; For Lifer DXP 2023.Q4.x, download 2023.Q4.7 or later; For Lifer DXP 7.4, download fix pack 112 or later (7.4.3.112); For Lifer Portal 7.4, download 7.4.3.112 or later.
  3. 3. Stop the Lifer application server.
  4. 4. Install the fix pack or upgrade following Lifer's standard patch installation process (using Lifer_patch_tool or deploying the new bundle).
  5. 5. Restart the application server.
  6. 6. Verify the fix by testing the redirect parameter in both Announcements and Alerts portlets to ensure XSS payloads are no longer executed.
Caveat Review Lifer's release notes for your target version for any breaking changes or deprecations before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43817 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-43817 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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