# CVE-2025-62241: Liferay Commerce Order Content Web is Vulnerable to Authorization Bypass Through User-Controlled Key

> Authenticated attackers can view shipment addresses from other virtual instances via IDOR in Liferay DXP.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Oct 2025
- **Updated:** 14 Oct 2025
- **Also known as:** GHSA-fhcw-px4q-pmvv

## What is CVE-2025-62241?

CVE-2025-62241 is a medium-severity missing authorization vulnerability in Liferay Digital Experience Platform, published on 13 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Insecure Direct Object Reference (IDOR) vulnerability with shipment addresses in Liferay DXP 2023.Q4.1 through 2023.Q4.5 allows remote authenticated users to from one virtual instance to view the shipment addresses of different virtual instance via the _com_liferay_commerce_order_web_internal_portlet_CommerceOrderPortlet_commerceOrderId parameter.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2025-62241?

2 open source packages ship an affected version, including com.liferay.commerce:com.liferay.commerce.order.content.web. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.liferay.commerce:com.liferay.commerce.order.content.web` | Maven | All versions | 4.0.114 |
| `com.liferay.commerce:com.liferay.commerce.order.content.web` | Maven | All versions | 4.0.114 |

Products: Liferay Digital Experience Platform.

## How do I fix CVE-2025-62241?

Upgrade com.liferay.commerce:com.liferay.commerce.order.content.web to 4.0.114 or later.

## Is CVE-2025-62241 being exploited?

There is no known exploitation of CVE-2025-62241 in the wild and no public exploit code.

## Other vulnerabilities in Liferay Digital Experience Platform

- [CVE-2024-8980](https://insights.sbomify.com/CVE-2024-8980/): Liferay Portal and Liferay DXP Vulnerable to CSRF in the Script Console (critical 9.6)
- [CVE-2023-42496](https://insights.sbomify.com/CVE-2023-42496/): Liferay Portal and Liferay DXP vulnerable to reflected Cross-site Scripting (critical 9.6)
- [CVE-2023-42498](https://insights.sbomify.com/CVE-2023-42498/): Liferay Portal Language Override edit screen and Liferay DXP vulnerable to reflected Cross-site Scripting (critical 9.6)
- [CVE-2024-25147](https://insights.sbomify.com/CVE-2024-25147/): Liferay Portal and Liferay DXP vulnerable to Cross-site Scripting (critical 9.6)
- [CVE-2024-26269](https://insights.sbomify.com/CVE-2024-26269/): Liferay Portal Frontend JS module's portlet.js and Liferay DXP vulnerable to Cross-site Scripting (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62241 and fix it if it is affected.

What it is: CVE-2025-62241 is a medium-severity missing authorization vulnerability in Liferay Digital Experience Platform, published on 13 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-62241 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.liferay.commerce:com.liferay.commerce.order.content.web (Maven): affected all versions; fixed in 4.0.114
- com.liferay.commerce:com.liferay.commerce.order.content.web (Maven): affected all versions; fixed in 4.0.114

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-62241/ (Markdown: https://insights.sbomify.com/CVE-2025-62241/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-62241
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-62241
- OSV: https://osv.dev/vulnerability/CVE-2025-62241

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-62241/
Summaries are generated and may contain mistakes; the official description above is the record.