dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43791

MEDIUM · 6.1 CVSS v3.1 Published 2025-09-15
Fix available
A fix is available. Upgrade to 7.4.3.112 / 2023.q3.5 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 cross-site scripting (XSS) vulnerabilities in Liferay Portal 7.3.0 through 7.4.3.111, and Liferay DXP 2023.Q4.0, 2023.Q3.1 through 2023.Q3.4, 7.4 GA through update 92 and 7.3 GA through update 36 allow remote attackers to inject arbitrary web script or HTML via a crafted payload injected into a "Rich Text" type field to (1) a web content structure, (2) a Documents and Media Document Type , or (3) custom assets that uses the Data Engine's module Rich Text field.

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

Cross-site scripting (XSS) vulnerability in Limerick Portal and DXP affecting Rich Text type fields in web content structures, Documents and Media Document Types, and custom assets using the Data Engine's Rich Text field. Attackers can inject arbitrary web script or HTML via crafted payloads in these input fields.

MitigationApply vendor patches/updates from Limerick for affected versions (7.3.x through update 36, 7.4.x through update 92/111, and DXP 2023.Q3.x through Q4.0). Until patched, restrict or sanitize user input in Rich Text fields and consider disabling untrusted user-generated content in affected areas.

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.5= 7.3= 7.4= 2023.q4.0
Liferay PortalApplication
Affected:< 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 Lifer Portal/DXP version
    Access the Lifer Control Panel or check the bundle version file (typically in the Lifer home directory or via the Server Info panel in the admin console). Look for the exact version number such as 7.3.x, 7.4.x, or a quarterly release like 2023.q3.x or 2023.q4.0.
    Affected if The installed version falls within 7.3 (all variants), 7.4 (all variants), 2023.q3.1 through 2023.q3.4, or 2023.q4.0; or for Lifer Portal: any version below 7.4.3.112.
  2. Check for Web Content Structures with Rich Text fields
    Navigate to Content & Data > Web Content > Structures in the Lifer admin panel. Review each structure definition and identify if any field uses the Rich Text input type.
    Affected if Any web content structure contains a Rich Text type field and the Lifer version is vulnerable.
  3. Check Documents and Media Document Types for Rich Text fields
    Navigate to Content & Data > Documents and Media > Document Types in the admin panel. Inspect each custom document type to see if it includes a Rich Text metadata field.
    Affected if Any custom Document Type includes a Rich Text field and the Lifer version is vulnerable.
  4. Check Data Engine custom assets for Rich Text fields
    Navigate to Design > Data Engine (or the applicable admin section for custom assets). Review asset definitions created with the Data Engine to identify any fields of type Rich Text.
    Affected if Any custom asset created via Data Engine contains a Rich Text field and the Lifer version is vulnerable.
  5. Assess user access to Rich Text input areas
    Review user roles and permissions to determine whether untrusted or non-administrative users have create or edit access to web content, documents, or custom assets that contain Rich Text fields.
    Affected if Untrusted users can create or edit content in Rich Text fields and the Lifer version is vulnerable.

You are affected if your Lifer Portal or DXP version matches the vulnerable ranges AND you have Rich Text fields enabled in web content structures, Documents and Media, or Data Engine assets that are accessible to untrusted users.

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.5 or later
Fixed in 7.4.3.1122023.q3.5
Interim mitigation

Apply vendor patches/updates from Limerick for affected versions (7.3.x through update 36, 7.4.x through update 92/111, and DXP 2023.Q3.x through Q4.0). Until patched, restrict or sanitize user input in Rich Text fields and consider disabling untrusted user-generated content in affected areas.

Recommended fix High confidence

Liferay Portal >= 7.4.3.112; DXP 2023.Q3.5+; DXP 2023.Q4.1+; DXP 7.3 update 37+; DXP 7.4 update 93+

  1. 1. Identify the specific Liferay product and version currently deployed (Liferay Portal or Liferay DXP)
  2. 2. For Liferay Portal 7.3.x: Upgrade to version 7.4.3.112 or later
  3. 3. For Liferay Portal 7.4.x: Upgrade to version 7.4.3.112 or later
  4. 4. For Liferay DXP 2023.Q3.x: Upgrade to version 2023.Q3.5 or later
  5. 5. For Liferay DXP 2023.Q4.0: Upgrade to a later patch set (2023.Q4.1 or later)
  6. 6. For Liferay DXP 7.3 GA: Apply update 37 or later
  7. 7. For Liferay DXP 7.4 GA: Apply update 93 or later
  8. 8. After upgrade, verify the Rich Text field input validation is working correctly by testing with XSS payloads
Caveat Minor - upgrade within same major version typically has minimal breaking changes; review Liferay release notes for any deprecation notices

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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