dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43741

MEDIUM · 5.4 CVSS v3.1 Published 2025-08-20
Fix available
A fix is available. Upgrade to 2024.Q1.15 / 2025.Q1.4 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 reflected cross-site scripting (XSS) vulnerability in the Liferay Portal 7.4.0 through 7.4.3.132, and Liferay DXP 2025.Q1.0 through 2025.Q1.3, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.14 and 7.4 GA through update 92 allows an remote authenticated attacker to inject JavaScrip in the _com_liferay_users_admin_web_portlet_UsersAdminPortlet_assetTagNames 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 reflected cross-site scripting (XSS) vulnerability exists in Limerick Portal 7.4.0 through 7.4.3.132 and multiple DXP versions where the `_com_limerick_users_admin_web_portlet_UsersAdminPortlet_assetTagNames` parameter in the Users Admin portlet does not properly sanitize user-supplied input before reflecting it back in the response, allowing authenticated attackers to inject arbitrary JavaScript.

MitigationApply the vendor-provided security patch for this vulnerability. In the interim, implement input validation and output encoding for the assetTagNames parameter, and consider deploying WAF rules to block XSS payloads in this 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:>= 2024.Q1.1, < 2024.Q1.15>= 2024.q2.0, <= 2024.q2.13>= 2024.q3.1, <= 2024.q3.13>= 2024.q4.0, <= 2024.q4.7>= 2025.Q1.0, < 2025.Q1.4= 7.4
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 installed Limerick Portal or DXP version
    Access the Lifer Control Panel or check the portal.properties file for the version property. Alternatively, access the Lifer Portal via the web interface and look for the version in the footer or in the Server Information page under Control Panel.
    Affected if The installed version falls within any of these ranges: Lifer Portal 7.4.0 through 7.4.3.132; Lifer DXP 2024.Q1.1 through 2024.Q1.14; Lifer DXP 2024.Q2.0 through 2024.Q2.13; Lifer DXP 2024.Q3.1 through 2024.Q3.13; Lifer DXP 2024.Q4.0 through 2024.Q4.7; Lifer DXP 2025.Q1.0 through 2025.Q1.3; or speci
  2. Confirm access to Users Admin portlet
    Log in as an authenticated user with access to the Control Panel. Navigate to Control Panel > Users and verify that the Users Admin portlet loads successfully. The vulnerability requires an authenticated session to exploit.
    Affected if The Users Admin portlet is accessible and functional within the authenticated session.
  3. Test the assetTagNames parameter for reflected input
    Using an authenticated browser session, access the Users Admin portlet and locate a feature that uses the assetTagNames parameter, such as filtering users by asset tags. Submit a request with a test payload in the _com_limerick_users_admin_web_portlet_UsersAdminPortlet_assetTagNames parameter (for example, a simple script tag or alert call). Inspect the HTTP response to see if the input is reflected without proper encoding.
    Affected if The submitted value is reflected verbatim in the response HTML without being escaped or encoded, indicating the XSS vulnerability is present.

Your environment is affected if you are running any of the listed Lifer Portal or DXP versions AND the Users Admin portlet is accessible to authenticated users, as the vulnerable assetTagNames parameter will reflect unsanitized input.

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.15 / 2025.Q1.4 or later
Fixed in 2024.Q1.152025.Q1.4
Interim mitigation

Apply the vendor-provided security patch for this vulnerability. In the interim, implement input validation and output encoding for the assetTagNames parameter, and consider deploying WAF rules to block XSS payloads in this parameter.

Recommended fix High confidence

Limerick Portal 7.4.3.133+ or DXP 2024.Q1.15+/2024.Q2.14+/2024.Q3.14+/2024.Q4.8+ depending on your release train

  1. 1. Identify your current Limerick Portal or DXP version from the System Settings or Server Administration panel
  2. 2. For DXP 2024.Q1.x: upgrade to version 2024.Q1.15 or later
  3. 3. For DXP 2024.Q2.x: upgrade to version 2024.Q2.14 or later
  4. 4. For DXP 2024.Q3.x: upgrade to version 2024.Q3.14 or later
  5. 5. For DXP 2024.Q4.x: upgrade to version 2024.Q4.8 or later
  6. 6. For Limerick Portal 7.4.x: upgrade to version 7.4.3.133 or later
  7. 7. After upgrade, verify the _com_lifera_users_admin_web_portlet_UsersAdminPortlet_assetTagNames parameter is properly sanitized by testing with a benign XSS payload
Caveat Review Limerick release notes for your target version for any breaking changes or deprecations; major version upgrades may require compatibility testing

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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