dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43787

MEDIUM · 5.4 CVSS v3.1 Published 2025-09-12
Fix available
A fix is available. Upgrade to 2024.q1.21 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.Q3.0, 2025.Q2.0 through 2025.Q2.12, 2025.Q1.0 through 2025.Q1.17, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.0 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13 and 2024.Q1.1 through 2024.Q1.20 allows an remote authenticated attacker to inject JavaScript through the organization site names. The malicious payload is stored and executed without proper sanitization or 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

Stored XSS vulnerability in Liferay Portal and DXP allows authenticated attackers to inject malicious JavaScript through organization site names. The payload is persisted in the database and executed without sanitization or escaping when other users view the affected content.

MitigationApply the vendor patch or upgrade to a fixed Liferay version; implement input validation on organization site name fields and consider Content Security Policy headers as defense-in-depth.

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.21>= 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.12= 2025.q3.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
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 Liferay version
    Access the Liferay Control Panel > Server Management > Server Information, or inspect the portal.properties file in the deployment, or check the WAR file version metadata. Liferet versions follow formats like 7.4.x.x or 2024.qX.X.
    Affected if The installed version falls within any of these ranges: 7.4.0 to 7.4.3.132; 2024.q1.1 to 2024.q1.21; 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.17; 2025.q2.0 to 2025.q2.12; or exactly 2025.q3.0
  2. Verify organizations with site functionality are in use
    Navigate to Control Panel > Users > Organizations. Review whether any organizations exist and whether the 'Site' option is enabled for those organizations (organization site creation is an optional feature).
    Affected if Organizations exist and at least one organization has an associated site enabled
  3. Inspect organization site names for potential XSS payloads
    In the Control Panel, examine each organization's details and site configuration. Specifically review the Site Name field. Alternatively, query the LayoutSet or Group table in the Liferet database for organization site entries and inspect the name field for HTML/script tags.
    Affected if Any organization site name contains unsanitized HTML, script tags, or JavaScript event handlers (for example, <script>, onclick=, onerror=, or javascript: URIs)
  4. Confirm the XSS is stored and executes without sanitization
    Create a test organization with a site name containing a benign payload such as <img src=x onerror=alert(1)>. Save it and then view the organization in a different browser session or by a different user to observe if the script executes.
    Affected if The payload renders as raw HTML/JavaScript rather than being escaped or neutralized when viewed by other users

You are affected if your Liferet Portal/DXP version matches the affected ranges AND organizations with sites are configured AND their site names contain unsanitized script content that executes when viewed.

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.21 or later
Fixed in 2024.q1.21
Interim mitigation

Apply the vendor patch or upgrade to a fixed Liferay version; implement input validation on organization site name fields and consider Content Security Policy headers as defense-in-depth.

Recommended fix Moderate confidence

Upgrade to the next minor release within your product line: Portal 7.4.3.133+, DXP 2024.Q1.21+, DXP 2024.Q2.14+, DXP 2024.Q3.14+, or DXP 2024.Q4.8+

  1. 1. Identify the exact Lifer product and version currently deployed (Portal or Digital Experience Platform, and the specific q-release version)
  2. 2. For Lifer Portal 7.4.0-7.4.3.132: upgrade to version 7.4.3.133 or later
  3. 3. For DXP 2024.Q1.1-2024.Q1.20: upgrade to 2024.Q1.21 or later
  4. 4. For DXP 2024.Q2.0-2024.Q2.13: upgrade to 2024.Q2.14 or later
  5. 5. For DXP 2024.Q3.0-2024.Q3.13: upgrade to 2024.Q3.14 or later
  6. 6. For DXP 2024.Q4.0-2024.Q4.7: upgrade to 2024.Q4.8 or later
  7. 7. After upgrade, verify that organization site name input fields properly sanitize HTML/JavaScript content
  8. 8. Test that the stored XSS payload in organization site names no longer executes
Caveat Review Lifer release notes for your target version for any breaking changes or deprecation notices; minor point releases typically have low risk

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