dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43811

MEDIUM · 5.4 CVSS v3.1 Published 2025-09-29
Fix available
A fix is available. Upgrade to 7.4.3.112 / 2023.Q3.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
Multiple stored cross-site scripting (XSS) vulnerability in the related asset selector in Liferay Portal 7.4.3.50 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.4, 2023.Q3.1 through 2023.Q3.7, and 7.4 update 50 through update 92 allows remote authenticated attackers to inject arbitrary web script or HTML via a crafted payload injected into an asset author’s (1) First Name, (2) Middle Name, or (3) Last Name 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

Stored XSS vulnerability in Liferays related asset selector component allows authenticated users to inject malicious JavaScript/HTML through the First Name, Middle Name, or Last Name fields of an asset author. The unsanitized input is stored and executed when other users view the affected asset.

MitigationApply proper input validation and output encoding to all asset author name fields in the related asset selector. Upgrade to Liferays patched versions where available.

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.8>= 2023.Q4.0, < 2023.Q4.5= 7.4
Liferay PortalApplication
Affected:>= 7.4.3.50, < 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
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. Check Liferays Portal version
    Navigate to Control Panel > Configuration > Server Administration > Version, or check the portal-ext.properties file for the version property, or examine the WAR file version in the deploy directory
    Affected if The installed version is >= 7.4.3.50 and < 7.4.3.112, or is 2023.Q3.x (>= 2023.Q3.1 and < 2023.Q3.8), or is 2023.Q4.x (>= 2023.Q4.0 and < 2023.Q4.5), or is exactly 7.4 (without specific patch level)
  2. Verify related asset selector is in use
    Search for portlets or widgets that utilize the asset selector functionality, typically found in Web Content, Blog, or Document and Media structures that reference author information
    Affected if The related asset selector component is deployed and accessible to authenticated users in the environment
  3. Inspect asset author name fields for existing XSS
    Query the database tables storing asset-related data (such as AssetEntry, AssetAuthor, or related tables) for HTML or script tags in First Name, Middle Name, or Last Name fields; alternatively, create a test asset and examine the author name fields through the UI for unescaped characters
    Affected if Any asset author names contain unescaped HTML tags like <script>, <img>, or javascript: URIs
  4. Review user permissions for asset creation
    Check Control Panel > Users and Permissions > Roles to see which authenticated roles have permissions to create or edit assets that use the related asset selector
    Affected if Authenticated users have the ability to create or modify assets containing author name fields

Your environment is affected if the installed Liferays version falls within the vulnerable ranges AND the related asset selector component is in use, which could allow stored XSS in asset author name fields to execute for other users viewing those assets.

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.8 / 2023.Q4.5 or later
Fixed in 7.4.3.1122023.Q3.82023.Q4.5
Interim mitigation

Apply proper input validation and output encoding to all asset author name fields in the related asset selector. Upgrade to Liferays patched versions where available.

Recommended fix High confidence

Lifteray Portal 7.4.3.112+ / DXP 2023.Q3.8+ / DXP 2023.Q4.5+ / DXP 7.4 update 93+

  1. Identify your current Lifteray Portal or DXP version by checking the Control Panel > Configuration > Server Administration > Version
  2. For Lifteray Portal 7.4.x users: Upgrade to version 7.4.3.112 or later
  3. For Lifteray DXP 2023.Q3 users: Upgrade to version 2023.Q3.8 or later
  4. For Lifteray DXP 2023.Q4 users: Upgrade to version 2023.Q4.5 or later
  5. For Lifteray DXP 7.4 (updates): Ensure update 93 or later is applied
  6. After upgrade, verify the fix by testing the asset author fields (First Name, Middle Name, Last Name) in the related asset selector
  7. Validate that existing functionality continues to work as expected

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
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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