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

Advisory record · `GHSA-fhcw-px4q-pmvv`

- **Identifiers:** `GHSA-fhcw-px4q-pmvv` · `CVE-2025-62241`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-639](https://cwe.mitre.org/data/definitions/639.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 13 Oct 2025
- **Updated:** 17 Nov 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 13 Oct 2025, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `com.liferay.commerce:com.liferay.commerce.order.content.web` (Maven): affected `<4.0.114`; fixed in `4.0.114`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Liferay Commerce Order Content Web (com.liferay.commerce:com.liferay.commerce.order.content.web) versions before 4.0.114 are affected. A remote authenticated user can exploit an insecure direct object reference to view shipment addresses belonging to a different virtual instance. Upgrade to version 4.0.114. The source gives few details on the specific conditions required.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 4.0: `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`, from CNA (Liferay)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0028, the 20th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:09 UTC: First seen by agentprime
- 31 Oct 2026, 15:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-fhcw-px4q-pmvv)

## Sources

- [GitHub Advisory Database: GHSA-fhcw-px4q-pmvv](https://github.com/advisories/GHSA-fhcw-px4q-pmvv)
- [OSV: GHSA-fhcw-px4q-pmvv](https://osv.dev/vulnerability/GHSA-fhcw-px4q-pmvv)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-62241>
- <https://github.com/liferay/liferay-portal/commit/53401963f02f593bbf555b4b321fdaeb59e03a53>
- <https://github.com/liferay/liferay-portal/commit/75c39ea518eb91b3b5cbb0576074ebbbfd805401>
- <https://liferay.atlassian.net/browse/LPE-17936>
- <https://liferay.dev/portal/security/known-vulnerabilities/-/asset_publisher/jekt/content/CVE-2025-62241>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-fhcw-px4q-pmvv>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-fhcw-px4q-pmvv/>. Everything for agents: <https://agentprime.io/llms.txt>.