dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-62263

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-27
Fix available
A fix is available. Upgrade to 7.4.3.104 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 Liferay Portal 7.3.7 through 7.4.3.103, and Liferay DXP 2023.Q3.1 through 2023.Q3.4, 7.4 GA through update 92, 7.3 service pack 3 through update 36 allow remote attackers to inject arbitrary web script or HTML via a crafted payload injected into an Account Role’s “Title” text field to (1) view account role page, or (2) select account role page. Multiple cross-site scripting (XSS) vulnerabilities in Liferay Portal 7.3.7 through 7.4.3.103, and Liferay DXP 2023.Q3.1 through 2023.Q3.4, 7.4 GA through update 92, 7.3 service pack 3 through update 36 allow remote attackers to inject arbitrary web script or HTML via a crafted payload injected into an Organization’s “Name” text field to (1) view account page, (2) view account organization page, or (3) select account organization page.

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 vulnerabilities in Lifer DXP/Portal allow remote attackers to inject malicious scripts via Account Role's 'Title' field and Organization's 'Name' field. The payloads execute when users view or interact with the affected account role pages and organization pages.

MitigationUpgrade to Lifer 7.4.3.104 or later, or apply the appropriate patches for DXP versions. Implement server-side input validation and output encoding for the Account Role Title and Organization Name fields as a compensating control.

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:= 7.3= 7.4= 2023.q3.1= 2023.q3.2= 2023.q3.3= 2023.q3.4
Liferay PortalApplication
Affected:>= 7.3.7, < 7.4.3.104

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. Check Lifer Portal/DXP version
    Locate the Lifer version file or access the Control Panel > Configuration > Server Information to identify the installed version. Common paths: [Lifer-home]/portal-impl/build.number or via Gogo shell command 'sm --long'
    Affected if The installed version matches 7.3.x, 7.4.x, 2023.q3.1-4, or is >= 7.3.7 and < 7.4.3.104
  2. Verify Account Roles feature is in use
    Access Control Panel > Users > Roles, or query the database table User_ (or Role_ table depending on schema) to see if custom account roles with Title fields exist. Check if Account Roles functionality is enabled in portal.properties: 'account.role.enbled=true'
    Affected if Account Roles are created or the feature is active in the environment
  3. Verify Organizations feature is in use
    Access Control Panel > Users > Organizations, or query the database table Organization_ to see if any organizations are defined
    Affected if Organizations exist in the system with custom names
  4. Inspect Account Role Title values for XSS payloads
    Query the database: SELECT * FROM AccountRole WHERE title LIKE '%<script%' OR title LIKE '%onerror%' OR title LIKE '%onload%' (or inspect via Control Panel > Users > Roles > Account Roles > [select role] > Details tab)
    Affected if The Account Role Title field contains unsanitized HTML/JavaScript such as <script>, event handlers like onerror/onload, or encoded variants
  5. Inspect Organization Name values for XSS payloads
    Query the database: SELECT * FROM Organization_ WHERE name LIKE '%<script%' OR name LIKE '%onerror%' OR name LIKE '%onload%' (or inspect via Control Panel > Users > Organizations > [select org] > Details tab)
    Affected if The Organization Name field contains unsanitized HTML/JavaScript such as <script>, event handlers like onerror/onload, or encoded variants

A user is affected if their Lifer version falls within the affected range AND they have Account Roles or Organizations configured, with malicious scripts present in the Title or Name fields respectively.

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.104 or later
Fixed in 7.4.3.104
Interim mitigation

Upgrade to Lifer 7.4.3.104 or later, or apply the appropriate patches for DXP versions. Implement server-side input validation and output encoding for the Account Role Title and Organization Name fields as a compensating control.

Recommended fix High confidence

Liferan Portal 7.4.3.104+ / Liferan Portal 7.3 SP36+ / Liferan DXP 2023.Q3.4+

  1. 1. Identify the exact Liferan product and version currently running (Portal or DXP, and specific version number)
  2. 2. For Liferan Portal 7.4.x: Upgrade to version 7.4.3.104 or later
  3. 3. For Liferan Portal 7.3.x: Upgrade to service pack 36 or later
  4. 4. For Liferan DXP 2023.Q3.x: Upgrade to version 2023.Q3.4 or later
  5. 5. For Liferan DXP 7.4 GA: Upgrade to update 93 or later
  6. 6. For Liferan DXP 7.3: Upgrade to service pack 36 or later
  7. 7. After upgrade, verify that the Account Role 'Title' and Organization 'Name' fields properly encode user input to prevent XSS
Caveat Review Liferan upgrade documentation for any breaking changes between versions; test thoroughly in non-production environment before deploying

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