# CVE-2020-25476: Liferay Portal Vulnerable to Cross-Site Scripting (XSS) via User Name Parameter > Attackers can inject malicious scripts via profile fields that execute in other users' calendars, potentially leading to privilege escalation if an admin views the calendar. - **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 7 Jan 2021 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-pvpg-9553-f979 ## What is CVE-2020-25476? CVE-2020-25476 is a medium-severity cross-site scripting vulnerability in Liferay Liferay Portal, published on 7 Jan 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Liferay CMS Portal version 7.1.3 and 7.2.1 have a blind persistent cross-site scripting (XSS) vulnerability in the user name parameter to Calendar. An attacker can insert the malicious payload on the username, lastname or surname fields of its own profile, and the malicious payload will be injected and reflected in the calendar of the user who submitted the payload. An attacker could escalate its privileges in case an admin visits the calendar that injected the payload. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2020-25476? 4 open source packages ship an affected version, including com.liferay.portal:release.portal.bom. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `com.liferay.portal:release.portal.bom` | Maven | All versions to 7.1.3 | None | | `com.liferay.portal:release.portal.bom` | Maven | All versions to 7.1.3 | None | | `com.liferay.portal:release.portal.bom` | Maven | From 7.2 to 7.2.1 | None | | `com.liferay.portal:release.portal.bom` | Maven | From 7.2 to 7.2.1 | None | Products: Liferay Liferay Portal. ## How do I fix CVE-2020-25476? No fix has been published for CVE-2020-25476 yet. Limit exposure of the affected software until one is available. ## Is CVE-2020-25476 being exploited? There is no known exploitation of CVE-2020-25476 in the wild and no public exploit code. ## Other vulnerabilities in Liferay Liferay Portal - [CVE-2020-7961](https://insights.sbomify.com/CVE-2020-7961/): Liferay Portal Deserialization of Untrusted Data (critical 9.8, exploited in the wild) - [CVE-2021-33990](https://insights.sbomify.com/CVE-2021-33990/): File upload in n/a (critical 9.8) - [CVE-2019-16891](https://insights.sbomify.com/CVE-2019-16891/): Liferay Portal Allows RCE via Deserialization of a JSON Payload (critical 9.8) - [CVE-2023-47797](https://insights.sbomify.com/CVE-2023-47797/): Liferay Portal XSS with `p_l_back_url_title` on edit content page (critical 9.6) - [CVE-2020-13445](https://insights.sbomify.com/CVE-2020-13445/): Liferay Portal and Liferay DXP Vulnerable to Arbitrary Code Execution (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-25476 and fix it if it is affected. What it is: CVE-2020-25476 is a medium-severity cross-site scripting vulnerability in Liferay Liferay Portal, published on 7 Jan 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2020-25476 in the wild and no public exploit code. Affected packages and fixed versions: - com.liferay.portal:release.portal.bom (Maven): affected all versions up to 7.1.3; no fix listed - com.liferay.portal:release.portal.bom (Maven): affected all versions up to 7.1.3; no fix listed - com.liferay.portal:release.portal.bom (Maven): affected from 7.2 up to 7.2.1; no fix listed - com.liferay.portal:release.portal.bom (Maven): affected from 7.2 up to 7.2.1; 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-2020-25476/ (Markdown: https://insights.sbomify.com/CVE-2020-25476/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-25476 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-25476 - OSV: https://osv.dev/vulnerability/CVE-2020-25476 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-25476/ Summaries are generated and may contain mistakes; the official description above is the record.