dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-62267

MEDIUM · 6.1 CVSS v3.1 Published 2025-10-31
Fix available
A fix is available. Upgrade to 7.4.3.112 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 web content template’s select structure page in Liferay Portal 7.4.3.35 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10, 7.4 update 35 through update 92 allow remote attackers to inject arbitrary web script or HTML via a crafted payload injected into a user’s (1) First Name, (2) Middle Name, or (3) Last Name text field.

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 exist in Lifier DXP/Portal's web content template select structure page where user profile fields (First Name, Middle Name, Last Name) are not properly sanitized before being rendered in templates. Attackers can inject malicious scripts that execute when other users view the affected content.

MitigationUpdate to the patched Lifier versions (Portal 7.4.3.112+, DXP 2023.Q4.11+, 2023.Q3.11+, or 7.4 update 93+) and implement proper input validation and output encoding for user profile fields in templates.

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.4= 2023.q3.1= 2023.q3.2= 2023.q3.3= 2023.q3.4= 2023.q3.5= 2023.q3.6= 2023.q3.7= 2023.q3.8= 2023.q3.9= 2023.q3.10= 2023.q4.0
Liferay PortalApplication
Affected:>= 7.4.3.35, < 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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 your Lifter Portal version
    Access the Control Panel > Configuration > System Information or check the osgi/state folder for the portal version bundle. Alternatively, check the portal-ext.properties file for the version information.
    Affected if The installed version is 7.4.3.35 through 7.4.3.111, or is any 7.4.x version, or is any 2023.q3.x version through 2023.q3.10, or is 2023.q4.0.
  2. Confirm DXP or Portal product type
    Check the product edition in the Control Panel > Configuration > System Information. Liferay DXP is the commercial Digital Experience Platform; Liferay Portal is the open-source version.
    Affected if The product is DXP 7.4, DXP 2023.q3.x through 2023.q3.10, DXP 2023.q4.0, or Portal 7.4.3.35 through 7.4.3.111.
  3. Verify web content templates are in use
    Navigate to Content & Data > Web Content > Structures and Templates in the Control Panel. Check if any web content structures or templates have been created.
    Affected if Web content structures and templates exist in the system.
  4. Inspect user profile field configuration
    Navigate to Control Panel > Users > Users and Organizations. View user profiles to see if First Name, Middle Name, or Last Name fields contain special characters, HTML tags, or script elements.
    Affected if User profile fields (First Name, Middle Name, Last Name) contain unencoded HTML or script tags that would execute when rendered in templates.

You are affected if your Liferay installation matches one of the affected version ranges AND web content templates are being used to render user profile fields that may contain unsanitized input.

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 or later
Fixed in 7.4.3.112
Interim mitigation

Update to the patched Lifier versions (Portal 7.4.3.112+, DXP 2023.Q4.11+, 2023.Q3.11+, or 7.4 update 93+) and implement proper input validation and output encoding for user profile fields in templates.

Recommended fix High confidence

Lifecycle Portal 7.4.3.112+ or Liferary DXP 2023.Q3.10+/2023.Q4.10+

  1. 1. Identify the current Lifecycle Portal or DXP version using the Server Administration panel or version.properties file
  2. 2. For Liferay Portal: upgrade to version 7.4.3.112 or later
  3. 3. For Liferay DXP 2023.Q3.x: upgrade to 2023.Q3.10 or later (which includes the fix in update 92+)
  4. 4. For Liferay DXP 2023.Q4.x: upgrade to 2023.Q4.10 or later
  5. 5. After upgrading, verify that the First Name, Middle Name, and Last Name fields in user profiles no longer accept unsanitized HTML/JavaScript input
  6. 6. Test the web content template's select structure page to confirm XSS is no longer possible

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