What is CVE-2025-62247?

CVE-2025-62247 is a low-severity missing authorization vulnerability in com.liferay:com.liferay.search.experiences.service (maven), affecting versions <= 3.0.84. No fixed version is listed yet. The application does not perform an authorization check before performing a sensitive operation.

Which versions of com.liferay:com.liferay.search.experiences.service are affected by CVE-2025-62247?

com.liferay:com.liferay.search.experiences.service (maven) versions <= 3.0.84 is affected.

Is there a fix for CVE-2025-62247?

No fixed version is listed for CVE-2025-62247 yet. Monitor the advisory for updates and apply mitigations in the interim.

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

Whether CVE-2025-62247 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-62247 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-62247

Q: Which versions of com.liferay:com.liferay.search.experiences.service are affected by CVE-2025-62247?

com.liferay:com.liferay.search.experiences.service (maven) versions <= 3.0.84 is affected.

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

No fixed version is listed for CVE-2025-62247 yet. Monitor the advisory for updates and apply mitigations in the interim.

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

Whether CVE-2025-62247 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-62247 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-62247?

No fixed version is listed yet. In the interim: Keep the dependency up to date. Ensure authorization checks are enforced consistently on all sensitive operations.

Summary

Liferay Portal and DXP are Missing Authorization in Collection Provider

Missing Authorization in Collection Provider component in the Liferay Portal 7.4.0 through 7.4.3.132, and Liferay DXP 2025.Q2.0 through 2025.Q2.9, 2025.Q1.0 through 2025.Q1.16, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.19 allows instance users to read and select unauthorized Blueprints through the Collection Providers across instances.

Impact

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

Affected versions

com.liferay:com.liferay.search.experiences.service (<= 3.0.84)

Security releases

Not available

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

No fixed version is listed for CVE-2025-62247 yet.

In the interim: Keep the dependency up to date. Ensure authorization checks are enforced consistently on all sensitive operations.

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

Frequently Asked Questions

What is CVE-2025-62247? CVE-2025-62247 is a low-severity missing authorization vulnerability in com.liferay:com.liferay.search.experiences.service (maven), affecting versions <= 3.0.84. No fixed version is listed yet. The application does not perform an authorization check before performing a sensitive operation.
Which versions of com.liferay:com.liferay.search.experiences.service are affected by CVE-2025-62247? com.liferay:com.liferay.search.experiences.service (maven) versions <= 3.0.84 is affected.
Is there a fix for CVE-2025-62247? No fixed version is listed for CVE-2025-62247 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is CVE-2025-62247 exploitable, and should I be worried? Whether CVE-2025-62247 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-62247 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-62247? No fixed version is listed yet. In the interim: Keep the dependency up to date. Ensure authorization checks are enforced consistently on all sensitive operations.