dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2023-42497

MEDIUM · 6.1 CVSS v3.1 Published 2023-10-17
Fix available
A fix is available. Upgrade to 7.4.3.86 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
Reflected cross-site scripting (XSS) vulnerability on the Export for Translation page in Liferay Portal 7.4.3.4 through 7.4.3.85, and Liferay DXP 7.4 before update 86 allows remote attackers to inject arbitrary web script or HTML via the `_com_liferay_translation_web_internal_portlet_TranslationPortlet_redirect` parameter.

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 reflected cross-site scripting (XSS) vulnerability exists in Liferay Portal 7.4.3.4 through 7.4.3.85 and Liferay DXP 7.4 before update 86 on the Export for Translation page. The vulnerability allows remote attackers to inject arbitrary web script or HTML via the _com_lifera_translation_web_internal_portlet_TranslationPortlet_redirect parameter.

MitigationUpgrade to Liferay Portal 7.4.3.86, Liferay DXP 7.4 update 86, or later versions which contain the fix for this vulnerability.

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
Liferay PortalApplication
Affected:>= 7.4.3.4, < 7.4.3.86

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 Liffel Portal or DXP version
    Check the installed Liffel Portal or DXP version. This is typically visible in the Control Panel under Configuration > Server Information, or by examining the bundle properties file (e.g., portal-impl.properties or the WAR manifest).
    Affected if The installed version is 7.4.3.4 through 7.4.3.85, or DXP 7.4 before update 86.
  2. Verify the Translation module is deployed
    Confirm that the Translation module (com_lifera_translation_web) is deployed and running. This can be checked in the Liffel Control Panel under Apps > App Manager, or via the OSGi console (g! ps | grep translation).
    Affected if The Translation portlet module is present in the deployment.
  3. Confirm Export for Translation page access
    Determine if users can access the Export for Translation functionality. Navigate to the Translation portlet (typically under Site Administration > Publishing > Translation) or check the portlet configuration for the presence of the export feature.
    Affected if The Export for Translation page is accessible to users, either anonymously or with authenticated access.
  4. Inspect for the vulnerable parameter in requests
    Review HTTP requests and logs for usage of the _com_lifera_translation_web_internal_portlet_TranslationPortlet_redirect parameter. This can be done by examining browser developer tools, proxy logs, or server access logs when the Translation portlet is used.
    Affected if The vulnerable redirect parameter is being used in requests to the Translation portlet.

The environment is affected if it runs Liffel Portal 7.4.3.4-7.4.3.85 or Liffel DXP 7.4 before update 86, has the Translation portlet deployed, and exposes the Export for Translation functionality to users.

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.86 or later
Fixed in 7.4.3.86
Interim mitigation

Upgrade to Liferay Portal 7.4.3.86, Liferay DXP 7.4 update 86, or later versions which contain the fix for this vulnerability.

Recommended fix High confidence

Lifer Portal 7.4.3.86 or Lifer DXP 7.4 update 86

  1. 1. Back up your current Lifer Portal or DXP installation and database
  2. 2. Download Lifer Portal 7.4.3.86 or later from the official Lifer downloads page
  3. 3. Stop the Lifer application server
  4. 4. Upgrade the Lifer Portal/DXP installation to version 7.4.3.86 (or DXP 7.4 update 86) following the official upgrade documentation
  5. 5. Start the application server and verify the Translation Portlet functionality works correctly
  6. 6. Test that the XSS vulnerability is remediated by verifying the redirect parameter is properly sanitized

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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