dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43800

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
Cross-site scripting (XSS) vulnerability in Objects in Liferay Portal 7.4.3.20 through 7.4.3.111, and Liferay DXP 2023.Q4.0, 2023.Q3.1 through 2023.Q3.4 and 7.4 GA through update 92 allows remote attackers to inject arbitrary web script or HTML via a crafted payload injected into an object with a rich text type 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 cross-site scripting (XSS) vulnerability in Liferays Objects feature where rich text type fields do not properly sanitize user input, allowing attackers to inject malicious scripts or HTML that persist and execute when other users view the affected object data.

MitigationSanitize and validate all input in rich text object fields with context-appropriate output encoding; apply Liferays security patches or upgrade to a fixed version outside the vulnerable ranges (7.4.3.20-7.4.3.111, DXP 2023.Q3.1-2023.Q3.4, 2023.Q4.0, 7.4 GA through update 92).

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.4= 2023.q4.0
Liferay PortalApplication
Affected:>= 7.4.3.20, < 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 Liferays product and version
    Check the installed version via Control Panel > Configuration > Server Administration > Product Information, or examine the portal-ext.properties file for version properties, or look at the bundle's manifest files
    Affected if The version is LPortal 7.4.3.20-7.4.3.111, or DXP 2023.q3.1-2023.q3.4, or DXP 2023.q4.0, or DXP 7.4 GA through update 92
  2. Confirm Objects feature is in use
    Navigate to Control Panel > Object Definition and list all defined objects, or query the ObjectDefinition table in the database for active object definitions
    Affected if Any custom Object definitions exist in the system
  3. Inspect Object fields for rich text types
    Open each Object definition and review the field types, specifically looking for fields configured with type 'Rich Text' or similar text area fields that accept HTML content
    Affected if Any Object definition contains rich text or HTML-type fields that accept user-submitted content
  4. Verify rich text fields accept external input
    Check the field definitions to confirm they are not read-only and are exposed through forms or APIs that allow end-user input
    Affected if Rich text fields are editable by users through forms, layouts, or APIs

The environment is affected if the installed Liferays version is within the vulnerable ranges AND Objects with user-editable rich text fields are configured.

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

Sanitize and validate all input in rich text object fields with context-appropriate output encoding; apply Liferays security patches or upgrade to a fixed version outside the vulnerable ranges (7.4.3.20-7.4.3.111, DXP 2023.Q3.1-2023.Q3.4, 2023.Q4.0, 7.4 GA through update 92).

Recommended fix High confidence

Lifer LPortal 7.4.3.112, Lifer DXP 2023.Q4.1, Lifer DXP 2023.Q3.5, or Lifer DXP 7.4 Update 93 (depending on product line)

  1. 1. Identify the currently installed Liferay product and exact version using the Lifer LPortal or DXP version information
  2. 2. For Lifer LPortal 7.4.3.20 through 7.4.3.111: upgrade to version 7.4.3.112 or later
  3. 3. For Lifer DXP 2023.Q4.0: upgrade to version 2023.Q4.1 or later
  4. 4. For Lifer DXP 2023.Q3.1 through 2023.Q3.4: upgrade to version 2023.Q3.5 or later
  5. 5. For Lifer DXP 7.4 GA through update 92: upgrade to update 93 or later
  6. 6. After upgrade, verify that the Object definitions with rich text type fields no longer accept unsanitized input
  7. 7. Test that the XSS payload is no longer executable in the Object rich text fields
Caveat Standard upgrade precautions apply - review release notes for your specific version for any configuration or compatibility changes

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 / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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