dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2022-26596

MEDIUM · 6.1 CVSS v3.1 Published 2022-04-25
Fix available
A fix is available. Upgrade to after 7.3.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 Journal module's web content display configuration page in Liferay Portal 7.1.0 through 7.3.3, and Liferay DXP 7.0 before fix pack 94, 7.1 before fix pack 19, and 7.2 before fix pack 8, allows remote attackers to inject arbitrary web script or HTML via web content template names.

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 cross-site scripting (XSS) vulnerability in Lifer Portal/DXP's Journal module allows remote attackers to inject arbitrary web script or HTML via malicious web content template names displayed on the web content display configuration page. The injected payload executes when other users view the affected configuration page.

MitigationApply the appropriate fix pack for the affected DXP version (94 for 7.0, 19 for 7.1, 8 for 7.2) or upgrade to Lifer Portal 7.4+; alternatively, implement input validation/sanitization on template 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.0= 7.1= 7.2
Liferay PortalApplication
Affected:>= 7.1.0, <= 7.3.3

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 Lifer Portal/DXP installation version
    Access the Lifer Control Panel, go to Configuration > Server Administration > Product Information, or check the portal-ext.properties file for the version property. Alternatively, examine the WAR file or Docker image version.
    Affected if The installed version is 7.0.x, 7.1.x, 7.2.x, 7.3.0 through 7.3.3, or any version between 7.1.0 and 7.3.3 inclusive.
  2. Verify Journal module is deployed and active
    Log in as an administrator, navigate to Site Administration > Content & Data > Web Content. Confirm the module loads and you can access the Web Content section.
    Affected if The Journal module is present and accessible in the Lifer installation.
  3. Inspect existing web content template names for XSS payloads
    In the Web Content section, go to the Templates tab. Review each template's name field for suspicious characters such as <script>, javascript:, onerror=, or HTML tags like <img>, <iframe>.
    Affected if Any template name contains unsanitized HTML or JavaScript code that could execute when displayed.
  4. Check web content display configurations for injected template references
    Navigate to the page containing web content display portlets. Edit the configuration of each display widget and examine the template name field in the display settings. Look for encoded or raw script tags in the template selection.
    Affected if The web content display configuration shows template names with embedded script or HTML elements.
  5. Review recent audit logs for template creation/modification
    Access the Lifer audit system via the Control Panel > Security > Audit, or check server logs for entries containing 'JournalTemplate' or 'TemplateService' with unusual input patterns.
    Affected if Audit logs show template modifications containing potential XSS payloads in name fields.

A user is affected if they run Lifer Portal 7.1.0 through 7.3.3 or DXP 7.0-7.2, have the Journal module enabled, and possess web content templates with unsanitized names containing script or HTML tags.

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 a release after 7.3.3
Interim mitigation

Apply the appropriate fix pack for the affected DXP version (94 for 7.0, 19 for 7.1, 8 for 7.2) or upgrade to Lifer Portal 7.4+; alternatively, implement input validation/sanitization on template name fields as a compensating control.

Recommended fix High confidence

Liferi Portal 7.4+ or Liferi DXP fix packs (7.0 FP94+, 7.1 FP19+, 7.2 FP8+)

  1. 1. Identify the current Liferi Portal or DXP version in production by checking the Liferi Portal Control Panel or server startup logs.
  2. 2. For Liferi Portal 7.1.x through 7.3.3: Upgrade to Liferi Portal 7.4 or later (7.4.x is the next major release after 7.3.x).
  3. 3. For Liferi DXP 7.0: Apply Fix Pack 94 or later.
  4. 4. For Liferi DXP 7.1: Apply Fix Pack 19 or later.
  5. 5. For Liferi DXP 7.2: Apply Fix Pack 8 or later.
  6. 6. After applying the fix pack or upgrade, restart the Liferi server.
  7. 7. Verify the fix by accessing the Journal module's web content display configuration page and confirming that template names are properly sanitized/encoded.
Caveat Major version upgrades to Liferi Portal 7.4 may introduce breaking changes; review Liferi's upgrade documentation and test in a staging environment 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
  • 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-2022-26596 — 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-26596 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