What is CVE-2025-43810?

CVE-2025-43810 is a medium-severity security vulnerability in com.liferay.commerce:com.liferay.commerce.service (maven), affecting versions < 11.0.164. It is fixed in 11.0.164.

Which versions of com.liferay.commerce:com.liferay.commerce.service are affected by CVE-2025-43810?

com.liferay.commerce:com.liferay.commerce.service (maven) versions < 11.0.164 is affected.

Is there a fix for CVE-2025-43810?

Yes. CVE-2025-43810 is fixed in 11.0.164. Upgrade to this version or later.

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

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

Q: Which versions of com.liferay.commerce:com.liferay.commerce.service are affected by CVE-2025-43810?

com.liferay.commerce:com.liferay.commerce.service (maven) versions < 11.0.164 is affected.

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

Yes. CVE-2025-43810 is fixed in 11.0.164. Upgrade to this version or later.

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

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

Upgrade com.liferay.commerce:com.liferay.commerce.service to 11.0.164 or later.

Summary

Liferay Portal and DXP allows users to add a note to a different virtual instance

Insecure Direct Object Reference (IDOR) vulnerability with commerce order notes in Liferay Portal 7.3.5 through 7.4.3.112, and Liferay DXP 2023.Q4.0 through 2023.Q4.8, 2023.Q3.1 through 2023.Q3.10, and 7.4 GA through update 92 allows remote authenticated users to from one virtual instance to add a note to an order in a different virtual instance via the _com_liferay_commerce_order_web_internal_portlet_CommerceOrderPortlet_commerceOrderId parameter.

Impact

Affected versions

com.liferay.commerce:com.liferay.commerce.service (< 11.0.164)

Security releases

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