Digital Experience PlatformApplication · Liferay

CVE-2022-25146

MEDIUM · 5.3 CVSS v3.1 Published 2022-03-03
Fix available
A fix is available. Upgrade to 7.4.3.9 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 Remote App module in Liferay Portal Liferay Portal v7.4.3.4 through v7.4.3.8 and Liferay DXP 7.4 before update 5 does not check if the origin of event messages it receives matches the origin of the Remote App, allowing attackers to exfiltrate the CSRF token via a crafted event message.

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 · moderate confidence

The Remote App module in Limerick Portal/DXP 7.4 fails to validate the origin of incoming event messages against the configured Remote App origin. This allows cross-origin attackers to send crafted event messages that can exfiltrate CSRF tokens from authenticated users, enabling CSRF attacks.

MitigationUpgrade to Limerick Portal 7.4.3.9+, Limerick DXP 7.4 Update 5+, or later versions which include origin validation for event messages in the Remote App module.

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.9

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Liferem Portal version
    Locate the Liferem Portal version in the control panel or check the portal properties file for the version number
    Affected if Version is 7.4.3.4 through 7.4.3.8 (or 7.4 for DXP) indicating it is within the vulnerable range
  2. Verify Remote App module is enabled
    Access the Liferem control panel and navigate to System Settings or the Remote App configuration section to confirm if any Remote App entries are configured
    Affected if Remote App module has at least one Remote App entry configured and active
  3. Inspect Remote App origin settings
    Open the Remote App configuration for each configured entry and check the Origin or Allowed Origins field to see if origin validation is configured
    Affected if The Origin field is empty, not set, or allows any origin (wildcard or undefined)
  4. Confirm authenticated users access
    Review whether the Liferem instance has authenticated users who can access pages containing Remote App widgets
    Affected if The portal has authenticated users and Remote App widgets are embedded in accessible pages

A user is affected if their Liferem Portal/DXP version falls within 7.4.3.4 to 7.4.3.8 AND the Remote App module is enabled with an unset or permissive origin configuration.

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.9 or later
Fixed in 7.4.3.9
Interim mitigation

Upgrade to Limerick Portal 7.4.3.9+, Limerick DXP 7.4 Update 5+, or later versions which include origin validation for event messages in the Remote App module.

Recommended fix High confidence

LPortal 7.4.3.9 or Lifer DXP 7.4 Update 5

  1. Backup your current LPortal/DXP installation and database
  2. Upgrade LPortal to version 7.4.3.9 or later
  3. If using Lifer DXP 7.4, upgrade to Update 5 or later
  4. After upgrade, verify the Remote App module functions correctly
  5. Test that event message origin validation is working as expected

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25146 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-25146 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