dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-62255

MEDIUM · 6.1 CVSS v3.1 Published 2025-10-23
Fix available
A fix is available. Upgrade to 7.3 / 7.4.3.102 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
Self Cross-site scripting (XSS) vulnerability on the edit Knowledge Base article page in Liferay Portal 7.4.0 through 7.4.3.101, and older unsupported versions, and Liferay DXP 2023.Q3.1 through 2023.Q3.5, 7.4 GA through update 92, and older unsupported versions allows remote attackers to inject arbitrary web script or HTML via a crafted payload injected into an attachment's filename.

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

Self XSS vulnerability in Liferay Portal and DXP allows authenticated users to inject malicious web scripts via crafted filenames when uploading attachments to Knowledge Base articles. The payload executes in the context of the user's own session when viewing or editing the KB article.

MitigationApply Liferays security patch for CVE-2025-62255; implement input validation and output encoding on attachment filenames in the KB article functionality.

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.3= 7.4= 2023.q3.1= 2023.q3.2= 2023.q3.3= 2023.q3.4= 2023.q3.5
Liferay PortalApplication
Affected:< 7.4.3.102

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 Lifford Portal or DXP version
    Access the Lifford Control Panel, go to Configuration > Server Information, or inspect the portal-ext.properties file for the version property. Alternatively, check the WAR file version if manually deployed.
    Affected if The installed version is < 7.4.3.102 for Lifford Portal, or matches 7.3, 7.4, or any 2023.q3.x version for DXP.
  2. Confirm Knowledge Base module is enabled
    Navigate to Control Panel > Apps > Lifford Marketplace or check the modules under the KB service in the Lifford OSGi console. Verify the com.knowledge.base.service bundle is active.
    Affected if The KB article functionality is installed and active in the environment.
  3. Check for existing KB article attachments
    Navigate to the Knowledge Base section via the Lifford UI or query the KBArticleAttachment table in the database. Identify any attachments associated with KB articles.
    Affected if There are attachments present on KB articles in the system.
  4. Inspect attachment filenames for unsanitized content
    Review the filenames of KB article attachments. Look for filenames containing HTML tags, script elements, or JavaScript event handlers (such as <script>, onerror=, onload=, img src=).
    Affected if Any attachment filename contains raw HTML or JavaScript code that would execute when the KB article is viewed.

A user is affected if their Lifford Portal version is below 7.4.3.102 (or DXP matches 7.3/7.4/2023.q3.x) AND the Knowledge Base module is active with attachments containing unsanitized filenames.

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.3 / 7.4.3.102 or later
Fixed in 7.37.4.3.102
Interim mitigation

Apply Liferays security patch for CVE-2025-62255; implement input validation and output encoding on attachment filenames in the KB article functionality.

Recommended fix High confidence

Liferay Portal 7.4.3.102; Liferay DXP 2023.Q3.6; Liferay DXP 7.4 update 93

  1. 1. Identify the currently installed Liferay product (Portal or DXP) and its exact version
  2. 2. For Liferay Portal users: Upgrade to version 7.4.3.102 or later
  3. 3. For Liferay DXP 2023.Q3.x users: Upgrade to version 2023.Q3.6 or later
  4. 4. For Liferay DXP 7.4 users: Upgrade to update 93 or later
  5. 5. Verify the upgrade by checking the Lifaxer Knowledge Base article edit page functionality
  6. 6. Confirm the attachment filename field now properly sanitizes input
Caveat Minor - ensure custom hook/extension compatibility with the new version before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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