# CVE-2025-3760: Liferay Cross-site Scripting vulnerability > Authenticated attackers can inject malicious JavaScript via radio button custom fields in Liferay Portal, potentially executing code in victim browsers. - **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 17 Apr 2025 - **Updated:** 4 Sep 2025 - **Also known as:** GHSA-qhp6-vp7c-g7xp ## What is CVE-2025-3760? CVE-2025-3760 is a medium-severity cross-site scripting vulnerability in Liferay Digital Experience Platform, published on 17 Apr 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link. ### Official description A stored cross-site scripting (XSS) vulnerability exists with radio button type custom fields in Liferay Portal 7.2.0 through 7.4.3.129, and Liferay DXP 2024.Q4.1 through 2024.Q4.7, 2024.Q3.1 through 2024.Q3.9, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.12, 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10, 7.4 GA through update 92, 7.3 GA through update 36, and 7.2 GA through fix pack 20 allows remote authenticated attackers to inject malicious JavaScript into a page. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2025-3760? 26 open source packages ship an affected version, including com.liferay.portal:release.dxp.bom and com.liferay.portal:release.portal.bom. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `com.liferay.portal:release.dxp.bom` | Maven | All versions | None | | `com.liferay.portal:release.dxp.bom` | Maven | All versions | None | | `com.liferay.portal:release.dxp.bom` | Maven | From 2023.Q3.1 to 2023.Q3.10 | None | | `com.liferay.portal:release.dxp.bom` | Maven | From 2023.Q3.1 to 2023.Q3.10 | None | | `com.liferay.portal:release.dxp.bom` | Maven | From 2023.Q4.0 to 2023.Q4.10 | None | | `com.liferay.portal:release.dxp.bom` | Maven | From 2023.Q4.0 to 2023.Q4.10 | None | | `com.liferay.portal:release.dxp.bom` | Maven | From 2024.Q1.1 | 2024.Q1.13 | | `com.liferay.portal:release.dxp.bom` | Maven | From 2024.Q1.1 | 2024.Q1.13 | | `com.liferay.portal:release.dxp.bom` | Maven | From 2024.Q2.0 to 2024.Q2.13 | None | | `com.liferay.portal:release.dxp.bom` | Maven | From 2024.Q2.0 to 2024.Q2.13 | None | | `com.liferay.portal:release.dxp.bom` | Maven | From 2024.Q3.1 | 2024.Q3.10 | | `com.liferay.portal:release.dxp.bom` | Maven | From 2024.Q3.1 | 2024.Q3.10 | | `com.liferay.portal:release.dxp.bom` | Maven | From 2024.Q4.1 | 2025.Q1.0 | | `com.liferay.portal:release.dxp.bom` | Maven | From 2024.Q4.1 | 2025.Q1.0 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.10 to 7.2.10.8 | None | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.10 to 7.2.10.8 | None | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.10.fp1 to 7.2.10.fp20 | None | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.10.fp1 to 7.2.10.fp20 | None | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.3.10.0 to 7.3.10.3 | None | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.3.10.0 to 7.3.10.3 | None | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.3.10.ep1 to 7.3.10.u36 | None | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.3.10.ep1 to 7.3.10.u36 | None | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.4.13.u1 to 7.4.13.u92 | None | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.4.13.u1 to 7.4.13.u92 | None | | `com.liferay.portal:release.portal.bom` | Maven | From 7.2.0 | 7.4.3.132 | | `com.liferay.portal:release.portal.bom` | Maven | From 7.2.0 | 7.4.3.132 | Products: Liferay Digital Experience Platform, Liferay Liferay Portal. ## How do I fix CVE-2025-3760? Upgrade com.liferay.portal:release.dxp.bom to a fixed version for your release line: 2024.Q1.13, 2024.Q3.10 or 2025.Q1.0. ## Is CVE-2025-3760 being exploited? There is no known exploitation of CVE-2025-3760 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-3760 and fix it if it is affected. What it is: CVE-2025-3760 is a medium-severity cross-site scripting vulnerability in Liferay Digital Experience Platform, published on 17 Apr 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2025-3760 in the wild and no public exploit code. Affected packages and fixed versions: - com.liferay.portal:release.dxp.bom (Maven): affected all versions; no fix listed - com.liferay.portal:release.dxp.bom (Maven): affected all versions; no fix listed - com.liferay.portal:release.dxp.bom (Maven): affected from 2023.Q3.1 up to 2023.Q3.10; no fix listed - com.liferay.portal:release.dxp.bom (Maven): affected from 2023.Q3.1 up to 2023.Q3.10; no fix listed - com.liferay.portal:release.dxp.bom (Maven): affected from 2023.Q4.0 up to 2023.Q4.10; no fix listed - com.liferay.portal:release.dxp.bom (Maven): affected from 2023.Q4.0 up to 2023.Q4.10; no fix listed - com.liferay.portal:release.dxp.bom (Maven): affected from 2024.Q1.1; fixed in 2024.Q1.13 - com.liferay.portal:release.dxp.bom (Maven): affected from 2024.Q1.1; fixed in 2024.Q1.13 - com.liferay.portal:release.dxp.bom (Maven): affected from 2024.Q2.0 up to 2024.Q2.13; no fix listed - com.liferay.portal:release.dxp.bom (Maven): affected from 2024.Q2.0 up to 2024.Q2.13; no fix listed - com.liferay.portal:release.dxp.bom (Maven): affected from 2024.Q3.1; fixed in 2024.Q3.10 - com.liferay.portal:release.dxp.bom (Maven): affected from 2024.Q3.1; fixed in 2024.Q3.10 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-3760/ (Markdown: https://insights.sbomify.com/CVE-2025-3760/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3760 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3760 - OSV: https://osv.dev/vulnerability/CVE-2025-3760 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-3760/ Summaries are generated and may contain mistakes; the official description above is the record.