dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43815

MEDIUM · 6.1 CVSS v3.1 Published 2025-09-29
Fix available
A fix is available. Upgrade to 7.4.3.111 / 2023.q4.3 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
Reflected cross-site scripting (XSS) vulnerability on the page configuration page in Liferay Portal 7.4.3.102 through 7.4.3.110, and Liferay DXP 2023.Q4.0 through 2023.Q4.2, and 2023.Q3.5 allows remote attackers to inject arbitrary web script or HTML via the com_liferay_layout_admin_web_portlet_GroupPagesPortlet_backURLTitle 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 confidence

Reflected cross-site scripting (XSS) vulnerability in Lifford Portal/DXP page configuration. The com_lifer_layout_admin_web_portlet_GroupPagesPortlet_backURLTitle parameter in the GroupPagesPortlet does not properly sanitize user input, allowing attackers to inject arbitrary JavaScript or HTML that executes in victim browsers via crafted URLs.

MitigationUpgrade to Lifford Portal 7.4.3.111 or later, or apply available DXP patches for affected versions. Until patched, implement input validation and output encoding on the backURLTitle parameter.

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.q4.0, < 2023.q4.3= 2023.q3.5
Liferay PortalApplication
Affected:>= 7.4.3.102, < 7.4.3.111

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. Check Lifford Portal/DXP version
    Access the Lifford control panel or check the bundle version file (typically in LIFERAY_HOME/portal-*.jar or via the Lifford Server Administration panel under 'Server Information')
    Affected if The installed version falls within 7.4.3.102 through 7.4.3.110 (inclusive), or is 2023.q4.0 through 2023.q4.2, or is exactly 2023.q3.5
  2. Identify if GroupPagesPortlet is deployed and exposed
    Navigate to the Lifford Admin console and check the list of active portlets under the Layout Administration section, or inspect the deployed web applications for com_lifer_layout_admin_web_portlet_GroupPagesPortlet
    Affected if The GroupPagesPortlet is deployed and accessible to users (authenticated or anonymous)
  3. Verify the backURLTitle parameter is accepted
    Access the GroupPagesPortlet configuration page (typically at /group-pages or similar admin URLs) and inspect the page source or use browser dev tools to see if the backURLTitle parameter is present in forms or URLs
    Affected if The backURLTitle parameter is present and accepts user-supplied values without visible output encoding

A user is affected if they run a Lifford Portal version between 7.4.3.102-7.4.3.110 or DXP versions 2023.q3.5 or 2023.q4.0-2023.q4.2 AND the GroupPagesPortlet with the vulnerable backURLTitle parameter is exposed in their environment

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.111 / 2023.q4.3 or later
Fixed in 7.4.3.1112023.q4.3
Interim mitigation

Upgrade to Lifford Portal 7.4.3.111 or later, or apply available DXP patches for affected versions. Until patched, implement input validation and output encoding on the backURLTitle parameter.

Recommended fix High confidence

Lifford Portal 7.4.3.111 or later; Lifford DXP 2023.Q4.3 or later

  1. 1. Identify the exact Lifford DXP or Portal version currently deployed using the Liffy Control Panel > Configuration > Server Information
  2. 2. For Lifford Portal 7.4.3.102-7.4.3.110: Upgrade to version 7.4.3.111 or later
  3. 3. For Lifford DXP 2023.Q4.0-2023.Q4.2: Upgrade to version 2023.Q4.3 or later
  4. 4. For Lifford DXP 2023.Q3.5: Upgrade to version 2023.Q4.3 or later (or the latest 2023.Qx release that includes the fix)
  5. 5. After upgrade, verify the fix by confirming the com_lilead_layout_admin_web_portlet_GroupPagesPortlet_backURLTitle parameter is properly sanitized on the page configuration page
  6. 6. Test that the page configuration functionality works correctly post-upgrade
Caveat Review Lifford compatibility matrix for major version jumps; some custom OSGi modules or theme extensions may require recompilation against new API

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

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43815 — 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-43815 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