dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2022-26597

MEDIUM · 6.1 CVSS v3.1 Published 2022-04-25
Fix available
A fix is available. Upgrade to 7.3 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
Cross-site scripting (XSS) vulnerability in the Layout module's Open Graph integration in Liferay Portal 7.3.0 through 7.4.0, and Liferay DXP 7.3 before service pack 3 allows remote attackers to inject arbitrary web script or HTML via the site name.

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

A cross-site scripting (XSS) vulnerability exists in Liferay Portal and DXP's Layout module Open Graph integration. The site name parameter is not properly sanitized, allowing remote attackers to inject arbitrary web script or HTML that will be executed in the context of other users' browsers when the Open Graph metadata is rendered.

MitigationUpgrade to Liferay Portal 7.4.1, Liferay DXP 7.3 Service Pack 3 or later. Alternatively, implement input validation and output encoding on the site name field within the Layout module's Open Graph 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
Liferay PortalApplication
Affected:>= 7.3.0, <= 7.4.0

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. Check Lifer Portal version
    Access the Lifer Portal control panel and navigate to Configuration > Server Administration > Version, or check the portal-ext.properties file for the version property. Alternatively, examine the WAR file's version metadata in the application server.
    Affected if The installed version is between 7.3.0 and 7.4.0 inclusive, or is version 7.3 for DXP, or is any version below 7.3 for DXP.
  2. Verify Open Graph integration is enabled
    Navigate to Site Administration > Configuration > Site Settings > Open Graph, or check the layout's openGraphEnabled property in the database table Layout_. Inspect the portal-ext.properties or OSGi configuration for com_liferay_layout_open_graph_web.internal.portlet.action.EditLayoutOpenGraphMVCActionCommand.
    Affected if Open Graph is enabled for any site or layout in the Lifer installation.
  3. Inspect site name configuration in Layout Open Graph
    Query the Layout_ table in the Lifer database for rows where openGraphEnabled is true, then check the openGraphTitle or related fields for the site name. Alternatively, access Site Administration > Configuration > Site Settings > Open Graph and view the Site Name field.
    Affected if The site name field contains unsanitized user-supplied input or special characters that could be interpreted as script tags.
  4. Review Open Graph metadata rendering
    Access the public page with Open Graph enabled and view the page source. Look for meta tags with property og:site_name or og:title. Alternatively, use the browser developer tools to inspect the rendered HTML head section.
    Affected if The rendered HTML contains unencoded HTML tags or script elements within the og:site_name or related meta tag content.

A user is affected if they are running Lifer Portal 7.3.0-7.4.0 or Lifer DXP 7.3 or earlier AND have Open Graph enabled with a site name containing unsanitized content that appears unescaped in the rendered page source.

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

Upgrade to Liferay Portal 7.4.1, Liferay DXP 7.3 Service Pack 3 or later. Alternatively, implement input validation and output encoding on the site name field within the Layout module's Open Graph functionality.

Recommended fix Moderate confidence

Lifford Portal 7.4.1+ or Lifford DXP 7.3 Service Pack 3+

  1. 1. Identify whether you are running Liferay Portal or Lifford DXP by checking your product version in the Control Panel.
  2. 2. If running Lifford Portal 7.3.x or 7.4.0, upgrade to Lifford Portal 7.4.1 or later as this version contains the fix for the Open Graph XSS vulnerability.
  3. 3. If running Lifford DXP 7.3, apply Lifford DXP 7.3 Service Pack 3 or later to remediate this vulnerability.
  4. 4. After upgrading, verify the fix by testing the Open Graph settings in the Layout module to confirm the site name field properly sanitizes input.
  5. 5. Additionally, validate that existing site names containing potential XSS payloads are reviewed and sanitized.
Caveat Standard upgrade considerations apply - review Lifford's upgrade documentation for any configuration or compatibility notes between versions

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
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,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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