dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-62265

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 7.4.3.112 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a stored XSS vulnerability in Lifer's Blogs widget where crafted <iframe> elements injected into the blog Content field are rendered without the sandbox attribute. This allows the iframe to execute scripts in the context of the parent page, enabling attackers to access cookies, session tokens, or perform actions on behalf of authenticated users.

MitigationImplement the sandbox attribute on all iframe elements rendered in blog content, and add input sanitization to strip or neutralize dangerous iframe attributes before storage. The sandbox attribute should be set to appropriate values (e.g., 'allow-scripts' without 'allow-same-origin' to prevent parent page access).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Digital Experience PlatformApplication
Affected:<= 7.4= 2023.q3.1= 2023.q3.2= 2023.q3.3= 2023.q3.4= 2023.q3.5= 2023.q3.6= 2023.q3.7= 2023.q3.8= 2023.q4.0= 2023.q4.1= 2023.q4.2
Liferay PortalApplication
Affected:>= 7.2.0, < 7.4.3.112

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Lifer Portal or DXP version
    Access the Lifer control panel or check the product version via the administration console. On Lifer Portal this is typically found under Control Panel > Configuration > Server Administration > Product Information, or by inspecting the bundle version properties.
    Affected if The installed version is Lifer Portal 7.2.0 through 7.4.3.111, or Lifer DXP 2023.q3.1 through 2023.q4.2, or any DXP version 7.4 or below (including 7.4.x versions before the fix).
  2. Confirm the Blogs widget is deployed and accessible
    Navigate to the site where Blogs functionality may be active. Verify that the Blogs application widget is added to a page or accessible through the content management system.
    Affected if The Blogs widget is present and users can create or view blog entries.
  3. Inspect rendered blog content HTML for iframe elements
    Create or view a blog post entry, then view the page source or inspect the DOM using browser developer tools. Search for any <iframe> tags embedded within the blog content area.
    Affected if The blog content renders <iframe> elements that were injected into the Content field.
  4. Verify iframe elements lack the sandbox attribute
    In the browser developer tools or page source, examine each <iframe> tag found in blog content. Check whether the sandbox attribute is present on the element.
    Affected if The <iframe> tags in blog content do NOT include the sandbox attribute, allowing scripts to execute in the parent page context.

If the Lifer version falls within the affected ranges AND the Blogs widget is in use AND iframe elements in blog content are rendered without a sandbox attribute, the environment is vulnerable to this stored XSS.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.4.3.112 or later
Fixed in 7.4.3.112
Interim mitigation

Implement the sandbox attribute on all iframe elements rendered in blog content, and add input sanitization to strip or neutralize dangerous iframe attributes before storage. The sandbox attribute should be set to appropriate values (e.g., 'allow-scripts' without 'allow-same-origin' to prevent parent page access).

Recommended fix High confidence

Lifer Portal 7.4.3.112 or later; Lifer DXP 2023.Q3.9+/2023.Q4.11+

  1. 1. Identify the current Liferay Portal or DXP version by checking the Lifer Control Panel > Configuration > Server Administration > Product Information
  2. 2. For Liferay Portal 7.2.0 through 7.4.3.111: Upgrade to Lifer Portal 7.4.3.112 or later
  3. 3. For Lifer DXP 2023.Q3.x: Upgrade to Lifer DXP 2023.Q3.9 or later
  4. 4. For Lifer DXP 2023.Q4.x: Upgrade to Lifer DXP 2023.Q4.11 or later
  5. 5. After upgrade, verify the Blogs widget properly sanitizes iframe elements with the sandbox attribute
  6. 6. Test that existing blog entries with iframe content render correctly with restricted sandbox permissions
Caveat Review customizations to the Blogs widget that may rely on unsandboxed iframe behavior; test compatibility with existing blog content containing iframes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62265 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-62265 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data