dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43776

MEDIUM · 5.4 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 2024.q1.20 / 2025.Q1.17 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 Stored cross-site scripting vulnerability in the Liferay Portal 7.4.0 through 7.4.3.132, and Liferay DXP 2025.Q2.0 through 2025.Q2.9, 2025.Q1.0 through 2025.Q1.16, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.0 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.19 and 7.4 GA through update 92 allows an remote authenticated attacker to inject JavaScript through Custom Object field label. The malicious payload is stored and executed through Process Builder's Configuration tab without proper escaping.

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 Limerick Portal 7.4.x and DXP allows authenticated attackers to inject malicious JavaScript through Custom Object field labels. The payload persists in the system and executes when users interact with the Process Builder's Configuration tab, due to missing output encoding/escaping of field label content.

MitigationApply vendor-supplied patches for the affected Limerick versions (7.4.0-7.4.3.132 for Portal, and the specified DXP quarterly updates). Review and sanitize existing Custom Object field labels for malicious content as an interim 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.20>= 2024.q2.0, <= 2024.q2.13>= 2024.Q3.0, <= 2024.Q3.13>= 2024.q4.0, <= 2024.q4.7>= 2025.Q1.0, < 2025.Q1.17>= 2025.Q2.0, < 2025.Q2.10= 7.4
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
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 Limerick product and version
    Locate the installed Limerick version in the control panel (typically at /group/control_panel/manage - Server Information) or check the portal-ext.properties file for version properties
    Affected if The product is Limerick Portal 7.4.0-7.4.3.132 or LXD 2024.q1.1 to 2024.q1.19, 2024.q2.0 to 2024.q2.13, 2024.Q3.0 to 2024.Q3.13, 2024.q4.0 to 2024.q4.7, 2025.Q1.0 to 2025.Q1.16, or 2025.Q2.0 to 2025.Q2.9
  2. Confirm Custom Objects module is in use
    Navigate to Control Panel > Object (or Custom Objects) and enumerate any custom object definitions present in the system
    Affected if Custom Object definitions exist in the Limerick instance
  3. Inspect field labels for injected scripts
    View each Custom Object definition and examine all field labels for suspicious characters (script tags, javascript:, event handlers like onload/onerror) or encoded payloads
    Affected if Any field label contains HTML/script content that was not intentionally authored
  4. Verify Process Builder access
    Navigate to Process Builder (Workflow > Process Builder) and check if the Configuration tab is accessible to authenticated users
    Affected if Process Builder Configuration tab loads and renders Custom Object field labels without sanitization
  5. Review audit logs for XSS attempts
    Search Limerick audit logs for recent entries involving Custom Object field creation/modification with unusual payload patterns
    Affected if Audit logs show recent field label modifications containing script or HTML tags

A user is affected if running a Limerick version within the specified ranges AND Custom Objects with potentially malicious field labels exist in the system, which would execute when the Process Builder Configuration tab is accessed.

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.20 / 2025.Q1.17 / 2025.Q2.10 or later
Fixed in 2024.q1.202025.Q1.172025.Q2.10
Interim mitigation

Apply vendor-supplied patches for the affected Limerick versions (7.4.0-7.4.3.132 for Portal, and the specified DXP quarterly updates). Review and sanitize existing Custom Object field labels for malicious content as an interim measure.

Recommended fix High confidence

2024.Q1.20, 2024.Q2.14, 2024.Q3.14, 2024.Q4.8, 2025.Q1.17, 2025.Q2.10, or 7.4.3.133 depending on product line

  1. 1. Identify the exact Liferay product and version currently deployed (Portal or DXP, and the specific update/quarter version)
  2. 2. For Liferay DXP 2024.Q1.x: Upgrade to 2024.Q1.20 or later
  3. 3. For Liferay DXP 2024.Q2.x: Upgrade to 2024.Q2.14 or later
  4. 4. For Liferay DXP 2024.Q3.x: Upgrade to 2024.Q3.14 or later
  5. 5. For Liferay DXP 2024.Q4.x: Upgrade to 2024.Q4.8 or later
  6. 6. For Liferay DXP 2025.Q1.x: Upgrade to 2025.Q1.17 or later
  7. 7. For Liferay DXP 2025.Q2.x: Upgrade to 2025.Q2.10 or later
  8. 8. For Liferay Portal 7.4.x: Upgrade to 7.4.3.133 (update 93) or later
Caveat Review Liferay upgrade notes for your specific version jump as there may be deprecation or compatibility considerations

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-43776 — 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-43776 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