dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43753

MEDIUM · 5.4 CVSS v3.1 Published 2025-08-21
Fix available
A fix is available. Upgrade to 2024.Q1.17 / 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.32 through 7.4.3.132, and Liferay DXP 2025.Q1.0 through 2025.Q1.7, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.1 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.16 and 7.4 update 32 through update 92 allows an remote authenticated user to inject JavaScript into the embedded message field from the form container.

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 exists in Liferay Portal and DXP where an authenticated user can inject malicious JavaScript into the embedded message field of a form container component. The unsanitized user input is reflected back in the HTTP response, allowing script execution in the context of other users' browsers.

MitigationApply the appropriate Lifer patch or upgrade to a fixed version outside the vulnerable ranges. Additionally, implement output encoding on all user-supplied input in form container message fields 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.17>= 2024.Q2.1, <= 2024.Q2.13>= 2024.q3.1, <= 2024.q3.13>= 2024.q4.0, <= 2024.q4.7>= 2025.Q1.0, < 2025.Q1.8= 7.4
Liferay PortalApplication
Affected:>= 7.4.3.32, <= 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 the installed Lifer Portal or DXP version
    Log into the Lifer Control Panel and navigate to Control Panel > Configuration > Server Administration > Product Information, or check the startup log file (typically named log.txt or startup.log in the Lifer home directory) where the version is printed during startup.
    Affected if The version displayed matches one of the vulnerable ranges: 7.4.3.32 through 7.4.3.132 (Portal); 2024.Q1.1 through 2024.Q1.17, 2024.Q2.1 through 2024.Q2.13, 2024.Q3.1 through 2024.Q3.13, 2024.Q4.0 through 2024.Q4.7, or 2025.Q1.0 through 2025.Q1.7 (DXP); or equals 7.4 (DXP).
  2. Confirm the presence of form container components with message fields
    Access the Lifer Pages admin interface and review any pages containing form container fragments or widgets. Check if any form containers have custom embedded messages configured in their message field properties.
    Affected if Form container components with custom message fields are actively used or configured on published pages.
  3. Verify authentication requirements are met
    Confirm that the Lifer instance has user authentication enabled and that regular authenticated users (not just administrators) have access to create or edit form container content.
    Affected if Non-administrator authenticated users can access and modify form container configurations or create content using form components.

You are affected if your installed Lifer Portal version is between 7.4.3.32 and 7.4.3.132, or your DXP version falls within any of the listed 2024.Q1.x through 2025.Q1.x ranges or equals 7.4, and you have form container components with message fields in use by authenticated 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 2024.Q1.17 / 2025.Q1.8 or later
Fixed in 2024.Q1.172025.Q1.8
Interim mitigation

Apply the appropriate Lifer patch or upgrade to a fixed version outside the vulnerable ranges. Additionally, implement output encoding on all user-supplied input in form container message fields as a defense-in-depth measure.

Recommended fix Moderate confidence

LPortal 7.4.3.133+ or DXP 2024.Q1.17+/2024.Q2.14+/2024.Q3.14+/2024.Q4.8+

  1. 1. Identify the currently running LPortal or DXP version using the Control Panel or Server Administration console
  2. 2. For LPortal 7.4.3.x users: upgrade to LPortal 7.4.3.133 or later
  3. 3. For DXP 2024.Q1.x users: upgrade to DXP 2024.Q1.17 or later
  4. 4. For DXP 2024.Q2.x users: upgrade to DXP 2024.Q2.14 or later
  5. 5. For DXP 2024.Q3.x users: upgrade to DXP 2024.Q3.14 or later
  6. 6. For DXP 2024.Q4.x users: upgrade to DXP 2024.Q4.8 or later
  7. 7. After upgrade, verify the fix by testing the form container's embedded message field with malicious payloads
  8. 8. Clear browser cache and restart the application server to ensure all components are updated
Caveat Standard upgrade considerations apply - review Lifera's upgrade notes for database schema changes and deprecated features

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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