Digital Experience PlatformApplication · Liferay

CVE-2025-62251

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-13

Fix available

A fix is available. Upgrade to 7.4.3.119 / 2023.q3.9 or later.

See remediation →

71/100

Remediation priority · Elevated

Remotely reachable Zero-click

Official description

NVD · unedited

Liferay Portal 7.3.0 through 7.4.3.119, and Liferay DXP 2023.Q3.1 through 2023.Q3.8, 2023.Q4.0 through 2023.Q4.5, 7.4 GA through update 92 and 7.3 GA though update 36 shows content to users who do not have permission to view it via the Menu Display Widget. This security flaw could result in sensitive information being exposed to unauthorized users.

Technical summary

dbcve analysis · high confidence

Lifera Portal and DXP contain an Insecure Direct Object Reference (IDOR) vulnerability in the Menu Display Widget. The widget fails to properly enforce permission checks before rendering content, allowing authenticated users without view permissions to access sensitive information through the widget's content display functionality.

MitigationUpgrade Lifera Portal to version 7.4.3.120 or later, or Lifera DXP to the appropriate patched version for each affected release (2023.Q3.9+, 2023.Q4.6+, update 93+, or update 37+). Alternatively, restrict access to the Menu Display Widget until patching can be completed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Digital Experience PlatformApplication

Affected:<= 7.4>= 2023.q3.1, < 2023.q3.9>= 2023.q4.0, < 2023.q4.6

Liferay PortalApplication

Affected:>= 7.3.0, < 7.4.3.119

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify Liferay product and version

Check the Liferay portal or DXP installation for its version number, typically found in the control panel, about page, or version.properties file in the Liferay installation directory

Affected if The installed version falls within: Liferay Portal 7.3.0 to 7.4.3.118 (exclusive), or Liferay DXP <= 7.4, or DXP 2023.q3.1 to 2023.q3.8, or DXP 2023.q4.0 to 2023.q4.5
Locate the Menu Display Widget

Access the Liferay portal administration interface and navigate to the widgets or site pages configuration to identify if the Menu Display Widget is added to any page or site

Affected if The Menu Display Widget is present and enabled on any page within the portal
Verify widget permission configuration

In the Liferay control panel, access the permissions settings for the Menu Display Widget and review which roles have view permissions assigned

Affected if The widget permissions allow authenticated users without explicit view rights to access the widget content, or permissions are set to a role that broader users possess than intended
Check for sensitive content access

Using a test account without view permissions for protected content, attempt to access pages containing the Menu Display Widget and observe whether content that should be restricted is rendered

Affected if Content that the test account should not be able to view is displayed through the Menu Display Widget

You are affected if running a Liferay Portal or DXP version within the affected ranges AND the Menu Display Widget is enabled with permissive access that allows users without proper view permissions to see restricted content.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 7.4.3.119 / 2023.q3.9 / 2023.q4.6 or later

Fixed in 7.4.3.1192023.q3.92023.q4.6

Interim mitigation

Upgrade Lifera Portal to version 7.4.3.120 or later, or Lifera DXP to the appropriate patched version for each affected release (2023.Q3.9+, 2023.Q4.6+, update 93+, or update 37+). Alternatively, restrict access to the Menu Display Widget until patching can be completed.

Recommended fix High confidence

Lifford Portal 7.4.3.119+ or Lifford DXP 2023.Q3.9+/2023.Q4.6+ or corresponding update releases (7.3 update 37+, 7.4 update 93+)

1. Identify the exact Lifford DXP/Portal version currently running using the Liffy Control Panel or the Gogo shell command "version"
2. For Lifford Portal 7.3.x: Upgrade to version 7.3.0 update 37 or later
3. For Lifford Portal 7.4.x: Upgrade to version 7.4.3.119 or later (specifically 7.4.3.119 is noted as fixed)
4. For Lifford DXP 2023.Q3.x: Upgrade to version 2023.Q3.9 or later
5. For Lifford DXP 2023.Q4.x: Upgrade to version 2023.Q4.6 or later
6. For Lifford DXP 7.4 GA: Apply update 93 or later
7. After upgrade, verify the Menu Display Widget permissions by testing with users who should and should not have access to ensure the fix is effective
8. Review user roles and permissions for Menu Display Widget content after upgrade to ensure proper access controls are in place

Caveat Major version upgrades may require compatibility testing of custom modules, themes, and workflows; review Lifford upgrade documentation for breaking changes between minor 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
Implementation8.0 h
Testing6.0 h
Review / QA3.0 h

21.0 hours of engineering $3,680

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

liferay.devVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-62251 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-62251?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 7.4.3.119 / 2023.q3.9 or later

Severity 6.5 Medium

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Digital Experience Platform

Remediation

Need this fixed?

Fix this in Digital Experience Platform 21 hrs · Moderate

Typical engagement from $3,680

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2025-62251 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References