# Liferay Portal and Liferay DXP Allows Templates to be Viewed via the UI or API

Advisory record · `GHSA-mf8h-grfg-j9j3`

- **Identifiers:** `GHSA-mf8h-grfg-j9j3` · `CVE-2024-25605`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-276](https://cwe.mitre.org/data/definitions/276.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 20 Feb 2024
- **Updated:** 29 Jul 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 20 Feb 2024, 09:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `com.liferay.portal:release.portal.bom` (Maven): affected `>=7.2.0, <7.4.3.5-ga5`; fixed in `7.4.3.5-ga5`
- `com.liferay.portal:release.dxp.bom` (Maven): affected `<7.2.10.fp17`; fixed in `7.2.10.fp17`

## Machine-written summary

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

> Liferay Portal 7.2.0 through 7.4.3.4 and Liferay DXP 7.4.13, 7.3 before service pack 3, and 7.2 before fix pack 17 are affected, along with older unsupported versions. The Journal module grants guest users view permission to web content templates by default, so a remote attacker can view any template through the UI or API without logging in. Upgrade Liferay Portal to 7.4.3.5-ga5 or later, or Liferay DXP to 7.2.10.fp17 or later.

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 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`, from CNA (Liferay)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0048, the 42nd percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:10 UTC: First seen by agentprime
- 31 Oct 2026, 15:10 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-mf8h-grfg-j9j3)

## Sources

- [GitHub Advisory Database: GHSA-mf8h-grfg-j9j3](https://github.com/advisories/GHSA-mf8h-grfg-j9j3)
- [OSV: GHSA-mf8h-grfg-j9j3](https://osv.dev/vulnerability/GHSA-mf8h-grfg-j9j3)
- <https://nvd.nist.gov/vuln/detail/CVE-2024-25605>
- <https://github.com/liferay/liferay-portal/commit/45ffb97de7ac475335215f2b6e86ebe1e7283ab4>
- <https://github.com/liferay/liferay-portal/commit/5eb426ecc49e036ad566e829b8a2132104f7130e>
- <https://github.com/liferay/liferay-portal>
- <https://liferay.dev/portal/security/known-vulnerabilities/-/asset_publisher/jekt/content/cve-2024-25605>

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-mf8h-grfg-j9j3>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-mf8h-grfg-j9j3/>. Everything for agents: <https://agentprime.io/llms.txt>.