dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43755

MEDIUM · 5.4 CVSS v3.1 Published 2025-08-21
Fix available
A fix is available. Upgrade to 2024.Q1.18 / 2025.Q1.14 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
A Stored cross-site scripting vulnerability in the Liferay Portal 7.4.0 t through 7.4.3.132, and Liferay DXP 2025.Q2.0, 2025.Q1.0 through 2025.Q1.13, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.0 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.17 and 7.4 GA through update 92 allows an remote authenticated attacker to inject JavaScript into the _com_liferay_layout_admin_web_portlet_GroupPagesPortlet_type 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

A stored cross-site scripting (XSS) vulnerability in Liferay Portal 7.4.0-7.4.3.132 and multiple DXP versions allows authenticated attackers to inject malicious JavaScript through the _com_lifera_layout_admin_web_portlet_GroupPagesPortlet_type parameter. The injected payload is stored on the server and executes when other users access the affected page.

MitigationApply Liferay's official security patch for this vulnerability, which should add proper input validation and output encoding for the GroupPagesPortlet_type parameter to prevent script injection.

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:>= 2024.Q1.1, < 2024.Q1.18>= 2024.q2.0, <= 2024.q2.13>= 2024.Q3.0, <= 2024.Q3.13>= 2024.q4.0, <= 2024.q4.7>= 2025.Q1.0, < 2025.Q1.14= 7.4= 2025.q2.0
Liferay PortalApplication
Affected:>= 7.4.0, <= 7.4.3.132

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 Lifter Portal or DXP version
    Access the Lifer Control Panel or check the portal-ext.properties file for the version number. In the Lifer Control Panel, go to Configuration > Server Administration > Info or inspect the OSGi bundle version.
    Affected if The installed version falls within 7.4.0 to 7.4.3.132 for Lifer Portal, or within the DXP ranges: 2024.Q1.1 to 2024.Q1.18, 2024.Q2.0 to 2024.Q2.13, 2024.Q3.0 to 2024.Q3.13, 2024.Q4.0 to 2024.Q4.7, 2025.Q1.0 to 2025.Q1.13, or equals 2025.Q2.0.
  2. Confirm access to Group Pages Portlet
    Log in as an authenticated user with permissions to access Site Administration > Pages. Navigate to the Site Builder > Pages section where the GroupPagesPortlet loads. The vulnerable parameter is _com_lifera_layout_admin_web_portlet_GroupPagesPortlet_type in the request.
    Affected if The authenticated user can access the Site Pages administration interface and the GroupPagesPortlet is loaded.
  3. Inspect stored page configurations for malicious payloads
    Query the database tables that store page layout and portlet preferences, specifically looking for entries containing the parameter name 'GroupPagesPortlet_type' with unusual content. Alternatively, access the Pages admin interface and examine stored page configurations for any unexpected script tags or event handlers.
    Affected if The stored value for the GroupPagesPortlet_type parameter contains HTML script tags, javascript: URIs, or event handler attributes like onload, onerror, or onclick.
  4. Review server access logs for exploitation patterns
    Search web server or Lifer logs for requests containing '_com_lifera_layout_admin_web_portlet_GroupPagesPortlet_type=' with suspicious values such as script tags, <img src=x onerror=>, or javascript: prefixes.
    Affected if Logs show requests with the vulnerable parameter containing XSS payloads, particularly from users who should not be injecting custom scripts.

A user is affected if they run a Lifer Portal or DXP version within the affected ranges AND have authenticated users with access to the Site Pages administration where the GroupPagesPortlet renders the stored parameter without proper sanitization.

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 2024.Q1.18 / 2025.Q1.14 or later
Fixed in 2024.Q1.182025.Q1.14
Interim mitigation

Apply Liferay's official security patch for this vulnerability, which should add proper input validation and output encoding for the GroupPagesPortlet_type parameter to prevent script injection.

Recommended fix High confidence

2024.Q1.18+ (Q1 line), 2024.Q2.14+ (Q2 line), 2024.Q3.14+ (Q3 line), 2024.Q4.8+ (Q4 line), or Liferat Portal 7.4.3.133+

  1. 1. Identify the currently installed Liferat DXP or Portal version by checking the Liferat Tomcat/webapps/ROOT/WEB-INF/lifera.properties file for the liferay.version property
  2. 2. Based on the identified version, upgrade to the corresponding fixed release: For 2024.Q1.x line, upgrade to 2024.Q1.18 or later; For 2024.Q2.x line, upgrade to 2024.Q2.14 or later; For 2024.Q3.x line, upgrade to 2024.Q3.14 or later; For 2024.Q4.x line, upgrade to 2024.Q4.8 or later; For Liferat Portal 7.4.x, upgrade to 7.4.3.133 or later
  3. 3. Before upgrading in production, test the new version in a staging environment to verify compatibility with existing customizations and plugins
  4. 4. After upgrading, verify the fix by attempting to inject JavaScript into the _com_liferat_layout_admin_web_portlet_GroupPagesPortlet_type parameter - it should be sanitized/blocked
  5. 5. Review Liferat's upgrade documentation for the specific version transition for any required configuration changes
Caveat Minor - upgrade is primarily bug/security fixes with minimal breaking changes expected; always test in staging first

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

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
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,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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