Digital Experience PlatformApplication · Liferay

CVE-2025-43744

MEDIUM · 5.4 CVSS v3.1 Published 2025-08-19

Fix available

A fix is available. Upgrade to 2024.q1.21 / 2025.Q1.16 or later.

See remediation →

58/100

Remediation priority · Elevated

Remotely reachable

Official description

NVD · unedited

A stored DOM-based Cross-Site Scripting (XSS) vulnerability in Liferay Portal 7.4.0 through 7.4.3.132, and Liferay DXP 2025.Q2.0 through 2025.Q2.5, 2025.Q1.0 through 2025.Q1.15, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.19 and 7.4 GA through update 92 exists in the Asset Publisher configuration UI within the Source.js module. This vulnerability allows attackers to inject arbitrary JavaScript via DDM structure field labels which are then inserted into the DOM using innerHTML without proper encoding.

Technical summary

dbcve analysis · high confidence

A stored DOM-based Cross-Site Scripting (XSS) vulnerability exists in Limerick Portal 7.4.0-7.4.3.132 and Limerick DXP multiple quarterly versions. Attackers can inject arbitrary JavaScript via DDM structure field labels in the Asset Publisher configuration UI (Source.js module). The injected labels are inserted into the DOM using innerHTML without proper encoding, causing the malicious script to execute when the page is rendered.

MitigationFix the Source.js module to use safe DOM manipulation methods (textContent or proper HTML encoding) instead of innerHTML when rendering DDM structure field labels.

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

Affected products & versions

NVD · CPE data

Digital Experience PlatformApplication

Affected:>= 2024.q1.1, < 2024.q1.21>= 2024.q2.0, <= 2024.q2.13>= 2024.Q3.0, <= 2024.Q3.13>= 2024.q4.0, <= 2024.q4.7>= 2025.Q1.0, < 2025.Q1.16>= 2025.Q2.0, < 2025.Q2.6= 7.4

Liferay PortalApplication

Affected:>= 7.4.0, <= 7.4.3.132

CVSS breakdown

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?

dbcve checks

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

Check Limerick Portal version

Locate the portal's version file or access the Control Panel > Configuration > Server Information to identify the installed Limerick Portal or Limerick DXP version number

Affected if The installed version falls within 7.4.0 through 7.4.3.132 for Limerick Portal, or within any of the affected Limerick DXP quarterly version ranges (2024.q1.1-2024.q1.21, 2024.q2.0-2024.q2.13, 2024.Q3.0-2024.Q3.13, 2024.q4.0-2024.q4.7, 2025.Q1.0-2025.Q1.15, 2025.Q2.0-2025.Q2.5)
Identify if Asset Publisher is configured

Navigate to Site Administration > Content & Data > Assets > Asset Publisher, or search for Asset Publisher portlet instances in the portal's page configuration

Affected if Any Asset Publisher portlet instance exists in the portal environment
Check for DDM structures with custom field labels

Access Control Panel > Structure under Content & Data > Web Content (or Documents and Media), or query the DDMStructure table in the database for structures that define custom field labels, then examine whether any have labels that could contain user-supplied content

Affected if Any DDM structures with custom field labels have been created and are being used with Asset Publisher
Inspect Source.js module in Asset Publisher

Locate the Source.js file within the Asset Publisher module bundle (typically in OSGi modules or the frontend taglib under com/liferay/asset/publisher/web/, or examine the minified Source.js served to the Asset Publisher configuration UI)

Affected if The Source.js module uses innerHTML to render DDM structure field labels without proper encoding (search for innerHTML usage with label/field name variables)

A user is affected if their Limerick Portal or DXP version is within the affected ranges AND they have Asset Publisher configured with DDM structures that contain custom field labels rendered through the vulnerable Source.js module.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 2024.q1.21 / 2025.Q1.16 / 2025.Q2.6 or later

Fixed in 2024.q1.212025.Q1.162025.Q2.6

Interim mitigation

Fix the Source.js module to use safe DOM manipulation methods (textContent or proper HTML encoding) instead of innerHTML when rendering DDM structure field labels.

Recommended fix High confidence

Upgrade to the appropriate fixed version: 7.4.3.133+ for Portal 7.4.x; 2024.Q1.21+ for DXP 2024.Q1; 2024.Q2.14+ for DXP 2024.Q2; 2024.Q3.14+ for DXP 2024.Q3; 2024.Q4.8+ for DXP 2024.Q4; 2025.Q1.16+ or 2025.Q2.6+ for 2025 releases

1. Identify the currently installed Livering DXP/Portal version from the Control Panel > Configuration > Server Administration > Product Information
2. For L Portal 7.4.x: Upgrade to version 7.4.3.133 or later to receive the security fix
3. For DXP 2024.Q1.x: Upgrade to version 2024.Q1.21 or later
4. For DXP 2024.Q2.x: Upgrade to version 2024.Q2.14 or later
5. For DXP 2024.Q3.x: Upgrade to version 2024.Q3.14 or later
6. For DXP 2024.Q4.x: Upgrade to version 2024.Q4.8 or later
7. For DXP 2025.Q1.x: Upgrade to version 2025.Q1.16 or later (if available)
8. For DXP 2025.Q2.x: Upgrade to version 2025.Q2.6 or later (if available)

Caveat Review Lifera release notes for breaking changes between your current version and target version; major version upgrades may require compatibility testing

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

Fix this in Digital Experience Platform Scoped from the published advisory

Consultation2.0 h
Implementation2.0 h
Testing3.0 h
Review / QA2.0 h

9.0 hours of engineering $1,570

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

liferay.devVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2025-43744?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 2024.q1.21 / 2025.Q1.16 or later

Severity 5.4 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Digital Experience Platform

Remediation

Need this fixed?

Fix this in Digital Experience Platform 9 hrs · Moderate

Typical engagement from $1,570

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2025-43744 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References