dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43771

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-08
Fix available
A fix is available. Upgrade to 7.4.3.112 / 2023.Q3.4 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 cross-site scripting (XSS) vulnerabilities in the Notifications widget in Liferay Portal 7.4.3.102 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.5 and 2023.Q3.1 through 2023.Q3.10 allow remote attackers to inject arbitrary web script or HTML via a crafted payload injected into (1) a user’s “First Name” text field, (2) a user’s “Middle Name” text field, (3) a user’s “Last Name” text field, (4) the “Other Reason” text field when flagging content, or (5) the name of the flagged 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

Multiple stored XSS vulnerabilities in the Notifications widget of Liferay Portal 7.4.3.102-7.4.3.111 and Limerick DXP 2023.Q3.x-2023.Q4.x allow authenticated users to inject arbitrary web script or HTML via user profile fields (First, Middle, Last Name) and content flagging fields (Other Reason, flagged content name).

MitigationImplement proper input validation and output encoding on all user-supplied fields in the Notifications widget to neutralize malicious script injection.

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.4>= 2023.q4.0, < 2023.q4.6
Liferay PortalApplication
Affected:>= 7.4.3.102, < 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. Identify installed Limerick DXP or LPortal version
    Access the Liferays Control Panel > Configuration > Server Administration > Product Information, or check the osgi/state directory for bundle versions, or review the portal-ext.properties file for version information.
    Affected if The version is >= 2023.Q3.1 and < 2023.Q3.4, OR >= 2023.Q4.0 and < 2023.Q4.6 for DXP, OR >= 7.4.3.102 and < 7.4.3.112 for Portal.
  2. Confirm Notifications widget is active
    Navigate to the Liferays Control Panel > Apps > Widgets, or inspect the site pages to verify the Notifications portlet/widget is deployed and accessible to authenticated users.
    Affected if The Notifications widget is enabled and accessible to authenticated users on the portal.
  3. Verify user profile field modification is possible
    Access My Account > Profile or Control Panel > Users and Organizations > [user] > Profile, and confirm the First Name, Middle Name, and Last Name fields are editable by authenticated users.
    Affected if Authenticated users can edit their own profile name fields (First, Middle, Last Name).
  4. Check content flagging functionality is enabled
    Navigate to content items (documents, blog entries, message board posts) and verify the flagging or reporting feature exists, or check the Alerts/Notifications preferences panel for content flagging options.
    Affected if The content flagging feature is enabled, allowing users to flag content and enter custom reasons.

You are affected if your Liferays version falls within the affected ranges AND the Notifications widget is active with accessible user profile fields or content flagging features.

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.4 / 2023.q4.6 or later
Fixed in 7.4.3.1122023.Q3.42023.q4.6
Interim mitigation

Implement proper input validation and output encoding on all user-supplied fields in the Notifications widget to neutralize malicious script injection.

Recommended fix High confidence

Lifford Portal 7.4.3.112+ or Lifford DXP 2023.Q3.4+ / 2023.Q4.6+

  1. 1. Identify the current Lifford Portal or DXP version in production using the Control Panel > Configuration > Server Administration > Product Information
  2. 2. For Lifford Portal 7.4.x: Upgrade to version 7.4.3.112 or later
  3. 3. For Lifford DXP 2023.Q3.x: Upgrade to version 2023.Q3.4 or later
  4. 4. For Lifford DXP 2023.Q4.x: Upgrade to version 2023.Q4.6 or later
  5. 5. After upgrade, verify the Notifications widget functions correctly and test that XSS payloads in First Name, Middle Name, Last Name, Other Reason, and flagged content name fields are properly sanitized
Caveat Review Lifford's upgrade notes for your version range as there may be compatibility considerations with custom plugins or dependencies

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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