# CVE-2025-43740: Liferay Portal has Stored Cross-Site Scripting Vulnerability via Message Boards Feature > Remote authenticated attackers can inject JavaScript via message boards, potentially leading to session hijacking or malicious actions. - **Severity:** Medium 4.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/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:** No - **Published:** 19 Aug 2025 - **Updated:** 19 Aug 2025 - **Also known as:** GHSA-22jp-w3cg-gvmm ## What is CVE-2025-43740? CVE-2025-43740 is a medium-severity cross-site scripting vulnerability in Liferay Digital Experience Platform, published on 19 Aug 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 vulnerability in the Liferay Portal 7.4.3.120 through 7.4.3.132, and Liferay DXP 2025.Q2.0 through 2025.Q2.8, 2025.Q1.0 through 2025.Q1.15, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.1 through 2024.Q2.13 and 2024.Q1.9 through 2024.Q1.19 allows an remote authenticated attacker to inject JavaScript through the message boards feature available via the web interface. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2025-43740? 2 open source packages ship an affected version, including com.liferay.portal:release.portal.bom. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `com.liferay.portal:release.portal.bom` | Maven | From 7.4.3.120-ga120 to 7.4.3.132-ga23 | None | | `com.liferay.portal:release.portal.bom` | Maven | From 7.4.3.120-ga120 to 7.4.3.132-ga23 | None | Products: Liferay Digital Experience Platform, Liferay Liferay Portal. ## How do I fix CVE-2025-43740? No fix has been published for CVE-2025-43740 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-43740 being exploited? There is no known exploitation of CVE-2025-43740 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-43740 and fix it if it is affected. What it is: CVE-2025-43740 is a medium-severity cross-site scripting vulnerability in Liferay Digital Experience Platform, published on 19 Aug 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-43740 in the wild and no public exploit code. Affected packages and fixed versions: - com.liferay.portal:release.portal.bom (Maven): affected from 7.4.3.120-ga120 up to 7.4.3.132-ga23; no fix listed - com.liferay.portal:release.portal.bom (Maven): affected from 7.4.3.120-ga120 up to 7.4.3.132-ga23; 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-2025-43740/ (Markdown: https://insights.sbomify.com/CVE-2025-43740/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-43740 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-43740 - OSV: https://osv.dev/vulnerability/CVE-2025-43740 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-43740/ Summaries are generated and may contain mistakes; the official description above is the record.