dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-62237

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-10
Fix available
A fix is available. Upgrade to 7.4.3.112 / 2023.q3.9 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
Stored cross-site scripting (XSS) vulnerability in Commerce’s view order page in Liferay Portal 7.4.3.8 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.8, and 7.4 update 8 through update 92 allows remote attackers to inject arbitrary web script or HTML via a crafted payload injected into an Account’s “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 vulnerability in Liferat Commerce's order view page allows attackers to inject malicious JavaScript/HTML into the Account Name field. The payload persists in the database and executes when administrators view the order page, enabling session hijacking or defacement.

MitigationUpgrade to Liferat Portal 7.4.3.112+, Liferat DXP 2023.Q4.6+, 2023.Q3.9+, or 7.4 update 93+. Apply output encoding to the Account Name field when rendered in the commerce order view.

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:>= 2023.q3.1, < 2023.q3.9>= 2023.q4.0, < 2023.q4.6= 7.4
Liferay PortalApplication
Affected:>= 7.4.3.8, < 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
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 Liferat Portal version
    Navigate to Control Panel > Configuration > Server Administration > Version, or check the portal-ext.properties file for the version property
    Affected if Version is >= 7.4.3.8 and < 7.4.3.112 (for Liferat Portal)
  2. Check Liferat DXP version
    Navigate to Control Panel > Configuration > Server Administration > Version, or check the portal-ext.properties file for the version property
    Affected if Version is 7.4 any update, or >= 2023.q3.1 and < 2023.q3.9, or >= 2023.q4.0 and < 2023.q4.6 (for Liferat DXP)
  3. Verify Commerce module is enabled
    Navigate to Control Panel > Apps > Liferat Marketplace or check if the Commerce module is installed and active in the instance
    Affected if Commerce module is installed and enabled
  4. Identify Account Name field in commerce orders
    Access the commerce order view page (typically via Commerce > Orders) and locate the Account Name field where buyer information is displayed
    Affected if The Account Name field exists and is rendered in the order view page
  5. Inspect order view page for unencoded output
    View the HTML source of the commerce order page and check if the Account Name value is rendered without proper HTML encoding (look for unescaped < > or " characters in the account name display)
    Affected if The Account Name field displays raw HTML/JavaScript without encoding

You are affected if your Liferat Portal version is 7.4.3.8 through 7.4.3.111, or your Liferat DXP version is 7.4, 2023.q3.1-8, or 2023.q4.0-5, AND the Commerce module is enabled allowing unencoded Account Name values to be stored and displayed in order pages.

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 / 2023.q3.9 / 2023.q4.6 or later
Fixed in 7.4.3.1122023.q3.92023.q4.6
Interim mitigation

Upgrade to Liferat Portal 7.4.3.112+, Liferat DXP 2023.Q4.6+, 2023.Q3.9+, or 7.4 update 93+. Apply output encoding to the Account Name field when rendered in the commerce order view.

Recommended fix High confidence

Lifera Digital Experience Platform 2023.Q3.9, 2023.Q4.6, 7.4 update 93+; Liferay Portal 7.4.3.112+

  1. 1. Identify the current Liferay DXP/Potal version by checking the liferay-version.properties file in the LIFERAY_HOME directory
  2. 2. For Digital Experience Platform 2023.Q3.x users: Upgrade to version 2023.Q3.9 or later
  3. 3. For Digital Experience Platform 2023.Q4.x users: Upgrade to version 2023.Q4.6 or later
  4. 4. For Digital Experience Platform 7.4 users: Upgrade to version 7.4 update 93 or later (or the next available update after 92)
  5. 5. For Liferay Portal 7.4.3.x users: Upgrade to version 7.4.3.112 or later
  6. 6. Before upgrading in production, test the upgrade in a staging environment to verify compatibility with customizations and plugins
  7. 7. After upgrade, verify that the Account Name field in Commerce properly sanitizes input and no XSS payloads execute
Caveat Major version upgrades may require compatibility testing with custom themes, hooks, and EXT plugins; review Liferays upgrade stability documentation before proceeding

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