dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43733

MEDIUM · 5.4 CVSS v3.1 Published 2025-08-18
Fix available
A fix is available. Upgrade to 2025.Q1.8 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.3.132, and Liferay DXP 2025.Q1.0 through 2025.Q1.7 allows a remote authenticated attacker to inject JavaScript code via the content page's name field. This malicious payload is then reflected and executed within the user's browser when viewing the "document View Usages" page.

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 in Liferay Portal and DXP allows authenticated attackers to inject malicious JavaScript payloads through the content page's name field. The payload executes when users view the 'document View Usages' page due to insufficient input sanitization and output encoding on the reflected parameter.

MitigationApply vendor-supplied patches for Liferra Portal 7.4.3.132 and DXP 2025.Q1.x. Until patched, implement input validation and context-aware output encoding on content page name parameters in the document usages view rendering logic.

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:>= 2025.Q1.0, < 2025.Q1.8
Liferay PortalApplication
Affected:= 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 Liferra Portal version
    Navigate to Liferra Portal's Control Panel > Configuration > Server Administration > Product Information, or check the OSGi bundle version via the Gogo shell command 'lb | grep liferay.portal', or inspect the portal-ext.properties file for the version property.
    Affected if The installed version is 7.4.3.132 (exact match) or is between 2025.Q1.0 and 2025.Q1.7 inclusive for DXP.
  2. Verify content page creation is enabled
    Check if users have the permission to create content pages by navigating to Control Panel > Users > Roles > and inspecting the Content Page Creator role permissions, or check the portal-ext.properties for 'journal.api.service.enabled=true' and 'layout.type.content.page.enabled=true'.
    Affected if Content pages can be created and the Content Page Creator role has active permissions.
  3. Confirm access to Documents and Media module
    Navigate to the Documents and Media application in the Control Panel and verify the 'View Usages' action is available on any uploaded document, or check that the 'dl.app.view.usages' permission is granted to user roles.
    Affected if The Documents and Media module is active and users have permissions to view document usages.
  4. Inspect the vulnerable parameter in document usages view
    When viewing a document's 'View Usages' page, examine the browser developer tools Network tab for requests containing the 'className' or 'title' parameter that reflects the content page name, and verify if special characters are being URL-encoded or HTML-encoded.
    Affected if The content page name parameter in the document usages view is not properly sanitized and reflects raw input in the response.

A user is affected if they are running Liferra Portal 7.4.3.132 or DXP 2025.Q1.0 through 2025.Q1.7, have content page functionality enabled, and users can access the Documents and Media View Usages feature.

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 2025.Q1.8 or later
Fixed in 2025.Q1.8
Interim mitigation

Apply vendor-supplied patches for Liferra Portal 7.4.3.132 and DXP 2025.Q1.x. Until patched, implement input validation and context-aware output encoding on content page name parameters in the document usages view rendering logic.

Recommended fix Moderate confidence

Lifer DXP 2025.Q1.8 (for DXP); contact Lifer support for Portal 7.4.3.132 fix version

  1. Plan and schedule an upgrade window for your Lifer DXP or Portal instance
  2. Back up your Lifer DXP/Portal database and files before proceeding with the upgrade
  3. For Lifer Digital Experience Platform: upgrade from version 2025.Q1.0 through 2025.Q1.7 to version 2025.Q1.8 which contains the security fix
  4. For Lifer Portal 7.4.3.132: upgrade to a version that includes the security fix (contact Lifer support for specific patched version guidance)
  5. After upgrade, verify the fix by testing the content page name field and 'document View Usages' page to confirm the XSS vulnerability is resolved
  6. Deploy the upgraded instance to production after successful testing
Caveat Review Lifer 2025.Q1.8 release notes for any compatibility or configuration changes 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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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