# CVE-2025-62256: Liferay Portal and DXP do not properly restrict access to OpenAPI > Remote attackers can access OpenAPI YAML files via crafted URLs due to improper access restrictions in Liferay Portal and DXP. - **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 Oct 2025 - **Updated:** 23 Oct 2025 - **Also known as:** GHSA-j82q-c85j-xw4w ## What is CVE-2025-62256? CVE-2025-62256 is a medium-severity missing authorization vulnerability in Liferay Digital Experience Platform, published on 23 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Liferay Portal 7.4.0 through 7.4.3.109, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.7, 7.4 GA through update 92, 7.3 GA through update 35, and older unsupported versions does not properly restrict access to OpenAPI in certain circumstances, which allows remote attackers to access the OpenAPI YAML file via a crafted URL. Weakness: CWE-862 (Missing Authorization) ## Which versions are affected by CVE-2025-62256? 2 open source packages ship an affected version, including com.liferay:com.liferay.portal.security.auth.verifier. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `com.liferay:com.liferay.portal.security.auth.verifier` | Maven | All versions | 6.0.26 | | `com.liferay:com.liferay.portal.security.auth.verifier` | Maven | All versions | 6.0.26 | Products: Liferay Digital Experience Platform, Liferay Liferay Portal. ## How do I fix CVE-2025-62256? Upgrade com.liferay:com.liferay.portal.security.auth.verifier to 6.0.26 or later. ## Is CVE-2025-62256 being exploited? There is no known exploitation of CVE-2025-62256 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-62256 and fix it if it is affected. What it is: CVE-2025-62256 is a medium-severity missing authorization vulnerability in Liferay Digital Experience Platform, published on 23 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-62256 in the wild and no public exploit code. Affected packages and fixed versions: - com.liferay:com.liferay.portal.security.auth.verifier (Maven): affected all versions; fixed in 6.0.26 - com.liferay:com.liferay.portal.security.auth.verifier (Maven): affected all versions; fixed in 6.0.26 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-62256/ (Markdown: https://insights.sbomify.com/CVE-2025-62256/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-62256 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-62256 - OSV: https://osv.dev/vulnerability/CVE-2025-62256 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-62256/ Summaries are generated and may contain mistakes; the official description above is the record.