# CVE-2024-25152: Liferay Portal Message Board widget and Liferay DXP vulnerable to stored Cross-site Scripting > Authenticated attackers can inject arbitrary scripts via attachment filenames in the Message Board widget, potentially compromising user sessions. - **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 21 Feb 2024 - **Updated:** 26 Aug 2024 - **Also known as:** GHSA-p28x-4r5h-ph6j ## What is CVE-2024-25152? CVE-2024-25152 is a critical cross-site scripting vulnerability in Liferay Digital Experience Platform, published on 21 Feb 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description Stored cross-site scripting (XSS) vulnerability in Message Board widget in Liferay Portal 7.2.0 through 7.4.2, and older unsupported versions, and Liferay DXP 7.3 before service pack 3, 7.2 before fix pack 17, and older unsupported versions allows remote authenticated users to inject arbitrary web script or HTML via the filename of an attachment. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2024-25152? 6 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 | From 7.2.0 | 7.2.10.fp17 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.0 | 7.2.10.fp17 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.3.0 | 7.3.10.u4 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.3.0 | 7.3.10.u4 | | `com.liferay.portal:release.portal.bom` | Maven | All versions to 7.4.2 | None | | `com.liferay.portal:release.portal.bom` | Maven | All versions to 7.4.2 | None | Products: Liferay Digital Experience Platform, Liferay Liferay Portal. ## How do I fix CVE-2024-25152? Upgrade com.liferay.portal:release.dxp.bom to a fixed version for your release line: 7.2.10.fp17 or 7.3.10.u4. ## Is CVE-2024-25152 being exploited? There is no known exploitation of CVE-2024-25152 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-2024-25152 and fix it if it is affected. What it is: CVE-2024-25152 is a critical cross-site scripting vulnerability in Liferay Digital Experience Platform, published on 21 Feb 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-25152 in the wild and no public exploit code. Affected packages and fixed versions: - com.liferay.portal:release.dxp.bom (Maven): affected from 7.2.0; fixed in 7.2.10.fp17 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.2.0; fixed in 7.2.10.fp17 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.3.0; fixed in 7.3.10.u4 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.3.0; fixed in 7.3.10.u4 - com.liferay.portal:release.portal.bom (Maven): affected all versions up to 7.4.2; no fix listed - com.liferay.portal:release.portal.bom (Maven): affected all versions up to 7.4.2; no fix listed 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-2024-25152/ (Markdown: https://insights.sbomify.com/CVE-2024-25152/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-25152 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-25152 - OSV: https://osv.dev/vulnerability/CVE-2024-25152 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-25152/ Summaries are generated and may contain mistakes; the official description above is the record.