What is CVE-2025-62251?

CVE-2025-62251 is a medium-severity incorrect permission assignment for critical resource vulnerability in com.liferay:com.liferay.site.navigation.menu.item.asset.vocabulary (maven), affecting versions < 1.0.23. It is fixed in 1.0.23. A file, directory, or other resource is assigned permissions that allow broader access than intended.

Is there a fix for CVE-2025-62251?

Yes. CVE-2025-62251 is fixed in 1.0.23. Upgrade to this version or later.

Is CVE-2025-62251 exploitable, and should I be worried?

Whether CVE-2025-62251 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-62251 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-62251

Q: Is there a fix for CVE-2025-62251?

Yes. CVE-2025-62251 is fixed in 1.0.23. Upgrade to this version or later.

Q: Is CVE-2025-62251 exploitable, and should I be worried?

Whether CVE-2025-62251 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-62251 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-62251?

Upgrade com.liferay:com.liferay.site.navigation.menu.item.asset.vocabulary to 1.0.23 or later.

Summary

Liferay has Incorrect Permission Assignment for Critical Resource

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.

Impact

A file, directory, or other resource is assigned permissions that allow broader access than intended. Typical impact: unauthorized read, modification, or execution of the resource.

Affected versions

com.liferay:com.liferay.site.navigation.menu.item.asset.vocabulary (< 1.0.23)

Security releases

com.liferay:com.liferay.site.navigation.menu.item.asset.vocabulary → 1.0.23 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade com.liferay:com.liferay.site.navigation.menu.item.asset.vocabulary to 1.0.23 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-62251? CVE-2025-62251 is a medium-severity incorrect permission assignment for critical resource vulnerability in com.liferay:com.liferay.site.navigation.menu.item.asset.vocabulary (maven), affecting versions < 1.0.23. It is fixed in 1.0.23. A file, directory, or other resource is assigned permissions that allow broader access than intended.
Which versions of com.liferay:com.liferay.site.navigation.menu.item.asset.vocabulary are affected by CVE-2025-62251? com.liferay:com.liferay.site.navigation.menu.item.asset.vocabulary (maven) versions < 1.0.23 is affected.
Is there a fix for CVE-2025-62251? Yes. CVE-2025-62251 is fixed in 1.0.23. Upgrade to this version or later.
Is CVE-2025-62251 exploitable, and should I be worried? Whether CVE-2025-62251 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-62251 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-62251? Upgrade com.liferay:com.liferay.site.navigation.menu.item.asset.vocabulary to 1.0.23 or later.