CVE-2025-62265: XSS
Cross-site scripting (XSS) vulnerability in the Blogs widget in Liferay Portal 7.4.0 through 7.4.3.111, and older unsupported versions, and Liferay DXP 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.8, 7.4 GA through update 92, 7.3 GA through update 36, and older unsupported versions allows remote attackers to inject arbitrary web script or HTML via a crafted <iframe> injected into a blog entry's “Content” text field
The Blogs widget in Liferay DXP does not add the sandbox attribute to <iframe> elements, which allows remote attackers to access the parent page via scripts and links in the frame page.
Other sources
Cross-site scripting (XSS) vulnerability in the Blogs widget in Liferay Portal 7.4.0 through 7.4.3.111, and older unsupported versions, and Liferay DXP 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.8, 7.4 GA through update 92, 7.3 GA through update 36, and older unsupported versions allows remote attackers to inject arbitrary web script or HTML via a crafted <iframe> injected into a blog entry's “Content” text field.
The Blogs widget in Liferay DXP does not add the sandbox attribute to <iframe> elements, which allows remote attackers to access the parent page via scripts and links in the frame page.
— GitHub
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-62265?
CVE-2025-62265 is classified as a high severity cross-site scripting (XSS) vulnerability.
How do I fix CVE-2025-62265?
To mitigate CVE-2025-62265, upgrade to Liferay Portal version 7.4.3.112 or later, or Liferay DXP version 2023.Q4.11 or later.
Which versions are affected by CVE-2025-62265?
CVE-2025-62265 affects Liferay Portal versions 7.4.0 to 7.4.3.111 and various versions of Liferay DXP including 2023.Q4.0 to 2023.Q4.10.
What are the potential impacts of CVE-2025-62265?
Exploitation of CVE-2025-62265 could allow an attacker to execute arbitrary JavaScript in the context of a user's session.
Is there a workaround for CVE-2025-62265?
There is no official workaround for CVE-2025-62265; the recommended action is to upgrade to a secure version.