dbcve.org
DxpApplication · Liferay

CVE-2022-38512

MEDIUM · 6.5 CVSS v3.1 Published 2022-09-22
Fix available
A fix is available. Upgrade to after 7.4.3.36 or later.
See remediation →
72/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
The Translation module in Liferay Portal v7.4.3.12 through v7.4.3.36, and Liferay DXP 7.4 update 8 through 36 does not check permissions before allowing a user to export a web content for translation, allowing attackers to download a web content page's XLIFF translation file via crafted URL.

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

The Translation module in Liferay Portal v7.4.3.12-v7.4.3.36 and Liferay DXP 7.4 update 8-36 lacks authorization checks on the translation export functionality, allowing attackers to craft URLs that download XLIFF translation files for any web content without proper permissions.

MitigationApply the vendor patch to add permission checks before allowing export of web content translation files, or upgrade to a fixed version if available.

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
DxpApplication
Affected:= 7.4
Liferay PortalApplication
Affected:>= 7.4.3.12, <= 7.4.3.36

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 Liferay Portal version
    Navigate to the Control Panel > Server Administration > Information, or check the portal-ext.properties file for the version number, or inspect the WAR file manifest
    Affected if Version is 7.4.3.12 through 7.4.3.36 inclusive
  2. Check Liferay DXP version
    Navigate to the Control Panel > Server Administration > Information, or check the Liferay Home directory for the version information in portal-ext.properties
    Affected if Version is 7.4 (update 8 through 36)
  3. Verify Translation module is present
    In the Control Panel, go to Apps > Liferay Store or check the OSGi console for the translation web module (com.liferet.translation.web)
    Affected if The Translation module (com.liferet.translation.web) is installed and active
  4. Confirm web content with translations exists
    In the Control Panel, navigate to Content > Web Content and check if any web content articles have translations enabled or have been translated
    Affected if Web content articles exist with translation records in the database
  5. Check for unauthorized translation export URLs
    Review web server access logs for requests to URLs containing '/translate/export Translation' or '/c/translate/export' pattern with web content article IDs
    Affected if Any such translation export requests were logged for web content the requesting user should not have access to

User is affected if running Liferay Portal 7.4.3.12-7.4.3.36 or Liferay DXP 7.4 update 8-36 AND the Translation module is installed with web content translations present in the system.

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.4.3.36
Interim mitigation

Apply the vendor patch to add permission checks before allowing export of web content translation files, or upgrade to a fixed version if available.

Recommended fix High confidence

Lifera Portal 7.4.4+ or Lifera DXP 7.4 update 37+

  1. 1. Identify all affected Liferay Portal (7.4.3.12-7.4.3.36) and Liferay DXP (7.4 update 8-36) instances in your environment
  2. 2. Schedule a maintenance window for the upgrade process
  3. 3. Back up the current Liferay database and configuration files
  4. 4. Download the latest Lifera Portal 7.4.4.x or Lifera DXP 7.4 update 37+ release from the official Lifera customer portal
  5. 5. Follow Lifera's standard upgrade documentation for your specific version
  6. 6. Deploy the new version to your test environment first and verify all customizations work
  7. 7. Deploy to production after successful testing
  8. 8. Verify the Translation module permission checks are working by attempting an unauthorized export (with non-admin user)
Caveat Review Lifera's release notes for breaking changes between 7.4.3.x and 7.4.4.x as there may be API or feature changes

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

Fix this in Dxp Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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