dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43765

MEDIUM · 6.1 CVSS v3.1 Published 2025-08-23
Fix available
A fix is available. Upgrade to 7.4.3.132 / 2024.Q1.14 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
A Stored cross-site scripting vulnerability in the Liferay Portal 7.4.0 through 7.4.3.131, and Liferay DXP 2024.Q4.0, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.13 and 7.4 GA through update 92 allows an remote non-authenticated attacker to inject JavaScript into the text field from a web content.

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 stored cross-site scripting (XSS) vulnerability in Lifer Portal 7.4.0 through 7.4.3.131 and Lifer DXP multiple versions allows unauthenticated remote attackers to inject malicious JavaScript into text fields within web content. The injected payload persists in the database and executes when other users view the affected web content.

MitigationApply the vendor-supplied patches for the affected Lifer Portal/DXP versions and implement output encoding/sanitization for web content text fields. Consider implementing Content Security Policy (CSP) headers as a defense-in-depth measure.

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.14>= 2024.q2.0, <= 2024.q2.13>= 2024.q3.1, <= 2024.q3.13= 7.4= 2024.q4.0
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
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. Check Lifer Portal version
    Log into the Lifer Portal Control Panel, navigate to Configuration > System Information > Platform, and note the version number. Alternatively, locate the portal-impl.jar in the application server and check the portal.version property in portal-impl.jar/com/lifer/portal/impl/build.properties.
    Affected if The installed version is >= 7.4.0 and < 7.4.3.132
  2. Check Lifer DXP version
    Log into the Lifer DXP Control Panel, navigate to Configuration > System Information > Platform, and note the version number. Check if it matches the affected DXP ranges: 2024.Q1.1 through 2024.Q1.13, 2024.q2.0 through 2024.q2.13, 2024.q3.1 through 2024.q3.13, 7.4, or 2024.q4.0.
    Affected if The installed version matches any of the affected DXP version ranges provided in the CVE (2024.Q1.x, 2024.q2.x, 2024.q3.x, 7.4, or 2024.q4.0)
  3. Verify if Web Content feature is in use
    Navigate to Lifer Portal/DXP Control Panel > Content & Data > Web Content and inspect whether any web content articles exist. The vulnerability affects text fields within web content, so this feature must be actively used for exploitation.
    Affected if Web Content articles exist in the system and users can create or edit web content text fields

You are affected if your Lifer Portal version is 7.4.0 through 7.4.3.131 (or your DXP version matches any of the 2024.Q1-Q4/7.4 affected ranges) AND the Web Content feature is being used, allowing stored XSS payloads to persist in web content text fields.

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.132 / 2024.Q1.14 or later
Fixed in 7.4.3.1322024.Q1.14
Interim mitigation

Apply the vendor-supplied patches for the affected Lifer Portal/DXP versions and implement output encoding/sanitization for web content text fields. Consider implementing Content Security Policy (CSP) headers as a defense-in-depth measure.

Recommended fix High confidence

Lifteray Portal: 7.4.3.132+ | DXP 2024.Q1: 2024.Q1.14+ | DXP 2024.Q2: 2024.Q2.14+ | DXP 2024.Q3: 2024.Q3.14+

  1. 1. Identify the exact Lifteray product and version running (Portal or DXP, and the specific version number)
  2. 2. For Liferay Portal 7.4.x users: Upgrade to version 7.4.3.132 or later
  3. 3. For Liferay DXP 2024.Q1.x users: Upgrade to version 2024.Q1.14 or later
  4. 4. For Liferay DXP 2024.Q2.x users: Upgrade to version 2024.Q2.14 or later
  5. 5. For Liferay DXP 2024.Q3.x users: Upgrade to version 2024.Q3.14 or later
  6. 6. After upgrading, verify the XSS vulnerability is resolved by testing web content text field input validation
Caveat Minor: Review custom web content templates after upgrade as XSS sanitization improvements may affect existing content rendering

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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