What is CVE-2025-43732?

CVE-2025-43732 is a medium-severity security vulnerability in com.liferay:com.liferay.roles.selector.web (maven), affecting versions < 5.0.32. It is fixed in 5.0.32.

Which versions of com.liferay:com.liferay.roles.selector.web are affected by CVE-2025-43732?

com.liferay:com.liferay.roles.selector.web (maven) versions < 5.0.32 is affected.

Is there a fix for CVE-2025-43732?

Yes. CVE-2025-43732 is fixed in 5.0.32. Upgrade to this version or later.

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

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

Q: Which versions of com.liferay:com.liferay.roles.selector.web are affected by CVE-2025-43732?

com.liferay:com.liferay.roles.selector.web (maven) versions < 5.0.32 is affected.

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

Yes. CVE-2025-43732 is fixed in 5.0.32. Upgrade to this version or later.

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

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

Upgrade com.liferay:com.liferay.roles.selector.web to 5.0.32 or later.

Summary

Liferay Portal Vulnerable to Insecure Direct Object Reference

Liferay Portal 7.4.0 through 7.4.3.132, and Liferay DXP 2025.Q1.0 through 2025.Q1.10, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.1 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.17 and 7.4 GA through update 92 is vulnerable to Insecure Direct Object Reference (IDOR) in the groupId parameter of the _com_liferay_roles_selector_web_portlet_RolesSelectorPortlet_groupId. When an organization administrator modifies this parameter id value, they can gain unauthorized access to user lists from other organizations.

Impact

Affected versions

com.liferay:com.liferay.roles.selector.web (< 5.0.32)

Security releases

com.liferay:com.liferay.roles.selector.web → 5.0.32 (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.roles.selector.web to 5.0.32 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-43732? CVE-2025-43732 is a medium-severity security vulnerability in com.liferay:com.liferay.roles.selector.web (maven), affecting versions < 5.0.32. It is fixed in 5.0.32.
Which versions of com.liferay:com.liferay.roles.selector.web are affected by CVE-2025-43732? com.liferay:com.liferay.roles.selector.web (maven) versions < 5.0.32 is affected.
Is there a fix for CVE-2025-43732? Yes. CVE-2025-43732 is fixed in 5.0.32. Upgrade to this version or later.
Is CVE-2025-43732 exploitable, and should I be worried? Whether CVE-2025-43732 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-43732 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-43732? Upgrade com.liferay:com.liferay.roles.selector.web to 5.0.32 or later.