dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43826

MEDIUM · 5.4 CVSS v3.1 Published 2025-09-30
Fix available
A fix is available. Upgrade to 7.4.3.113 / 2023.Q4.9 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
Stored cross-site scripting (XSS) vulnerabilities in Web Content translation in Liferay Portal 7.4.0 through 7.4.3.112, and older unsupported versions, and Liferay DXP 2023.Q4.0 through 2023.Q4.8, 2023.Q3.1 through 2023.Q3.10, 7.4 GA through update 92, and older unsupported versions allow remote attackers to inject arbitrary web script or HTML via any rich text field in a web content article.

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 cross-site scripting (XSS) vulnerability in Liferar's Web Content translation feature. The vulnerability allows remote attackers to inject malicious web scripts or HTML into rich text fields within web content articles, which are then stored and executed when other users view the translated content.

MitigationUpgrade to the patched Liferay version as specified in the vendor advisory. In the interim, implement output encoding and implement strict input validation on all rich text fields within the Web Content translation module.

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.10>= 2023.Q4.0, < 2023.Q4.9>= 2024.Q1.1, < 2024.Q1.3
Liferay PortalApplication
Affected:>= 7.2.0, < 7.4.3.113

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 Liferar's installed version
    Access the Liferay administration control panel, typically at /group/control_panel/manage, and locate the Server Information section. Alternatively, check the portal-ext.properties file for the version property or examine the liferay-portal.war file metadata.
    Affected if The installed version is 7.4.3.113 or higher (for 7.4.x branch), or falls within 2023.Q3.1 through 2023.Q3.10, 2023.Q4.0 through 2023.Q4.8, or 2024.Q1.1 through 2024.Q1.2. Versions 7.2.0 through 7.4.3.112 are also affected.
  2. Confirm Web Content module is deployed
    Navigate to Content > Web Content in the Lifteray control panel sidebar. Verify that the Web Content application is accessible and listed among available applications.
    Affected if The Web Content application is present and accessible in the control panel.
  3. Verify translation feature is in use
    Open any existing Web Content article and look for the translation option, typically found in the article editor toolbar or article settings. Check if translation functionality is enabled in Portal Settings > Instance Settings > Localization.
    Affected if The translation feature is enabled or any translated Web Content articles exist in the system.
  4. Inspect stored content for suspicious scripts
    Use the Web Content admin interface to view raw HTML content of articles, or query the JournalArticle table in the database to examine the content_html field for unescaped script tags, iframe elements, or event handlers like onload, onerror, or onclick.
    Affected if Any Web Content articles contain raw script tags, JavaScript URLs, or HTML event handlers in the stored content that were not intentionally added by administrators.

A user is affected if their Liferay version falls within the vulnerable ranges AND the Web Content translation feature is enabled or being used, allowing stored malicious scripts to execute when translated content is viewed.

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.113 / 2023.Q4.9 / 2024.Q1.3 or later
Fixed in 7.4.3.1132023.Q4.92024.Q1.3
Interim mitigation

Upgrade to the patched Liferay version as specified in the vendor advisory. In the interim, implement output encoding and implement strict input validation on all rich text fields within the Web Content translation module.

Recommended fix High confidence

Lifer Portal 7.4.3.113 or later; Lifer DXP 2023.Q3.11+, 2023.Q4.9+, or 2024.Q1.3+ depending on your release line

  1. 1. Identify the current Lifter Portal or DXP version by checking the control panel or server logs
  2. 2. For Lifer Portal 7.4.x: upgrade to version 7.4.3.113 or later
  3. 3. For Lifer DXP 2023.Q3.x: upgrade to version 2023.Q3.11 or later
  4. 4. For Lifer DXP 2023.Q4.x: upgrade to version 2023.Q4.9 or later
  5. 5. For Lifer DXP 2024.Q1.x: upgrade to version 2024.Q1.3 or later
  6. 6. After upgrading, verify the patch was applied by checking the product version in the control panel
  7. 7. Test the Web Content translation functionality to confirm the XSS vulnerability is remediated
Caveat Review Lifer release notes for your target version to check for any breaking changes or deprecations between your current and target version

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

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43826 — 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-43826 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