Digital Experience PlatformApplication · Liferay

CVE-2025-43757

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

Fix available

A fix is available. Upgrade to 2024.Q1.19 / 2025.Q1.15 or later.

See remediation →

58/100

Remediation priority · Elevated

Remotely reachable

Official description

NVD · unedited

A reflected cross-site scripting (XSS) vulnerability in the Liferay Portal 7.4.0 through 7.4.3.132, and Liferay DXP 2025.Q2.0 through 2025.Q2.2, 2025.Q1.0 through 2025.Q1.14, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.1 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.18 and 7.4 GA through update 92 allows a remote authenticated attacker to inject JavaScript code via _com_liferay_dynamic_data_mapping_web_portlet_DDMPortlet_definition parameter.

Technical summary

dbcve analysis · high confidence

Reflected XSS in Liferay Portal/DXP via the _com_liferay_dynamic_data_mapping_web_portlet_DDMPortlet_definition parameter. An authenticated remote attacker can inject malicious JavaScript that executes in the victim's browser when the crafted parameter value is processed and reflected in the response without proper output encoding.

MitigationApply available vendor patches for the specific version (7.4.3.133+ for Portal, appropriate updates for DXP versions) and/or implement output encoding for the definition parameter in the DDMPortlet to prevent script execution.

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.19>= 2024.Q2.1, <= 2024.Q2.13>= 2024.q3.1, <= 2024.q3.13>= 2024.q4.0, <= 2024.q4.7>= 2025.Q1.0, < 2025.Q1.15>= 2025.Q2.0, < 2025.Q2.3= 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.

Identify Lifer Portal/DXP installation version

Check the Lifer installation directory for version files, or access the Lifer control panel and navigate to Account > Account Settings > Platform to view the installed version. Alternatively, check the portal-ext.properties file or the OSGi bundle metadata for version information.

Affected if The installed version falls within the affected ranges: DXP versions 2024.Q1.1 to 2024.Q1.18, 2024.Q2.1 to 2024.Q2.13, 2024.q3.1 to 2024.q3.13, 2024.q4.0 to 2024.q4.7, 2025.Q1.0 to 2025.Q1.14, 2025.Q2.0 to 2025.Q2.2, or version 7.4; or Portal versions 7.4.0 to 7.4.3.132.
Confirm DDMPortlet module is deployed

In the Lifer control panel, navigate to Apps > App Manager and verify that the dynamic-data-mapping-web bundle is installed. Alternatively, access the OSGi console and list bundles containing 'dynamic-data-mapping-web' in the name.

Affected if The dynamic-data-mapping-web module is present in the Lifer installation.
Check if user authentication is possible

Verify that user accounts exist and can authenticate to the Lifer Portal/DXP. Attempt to log in with a valid user account through the sign-in portlet.

Affected if Authentication to the portal is possible, as the vulnerability requires an authenticated attacker.
Identify exposed DDMPortlet endpoints

Review the web.xml descriptor or the portlet.xml configuration for the DDMPortlet definition. Check if the portlet is exposed on a public-facing page by browsing the site and looking for Dynamic Data Mapping forms or structures.

Affected if The DDMPortlet is accessible to authenticated users, particularly those with permissions to manage data definitions.

A user is affected if they are running an Lifer Portal version 7.4.0-7.4.3.132 or an Lifer DXP version within the specified ranges AND the DDMPortlet is accessible to authenticated users in their environment.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 2024.Q1.19 / 2025.Q1.15 / 2025.Q2.3 or later

Fixed in 2024.Q1.192025.Q1.152025.Q2.3

Interim mitigation

Apply available vendor patches for the specific version (7.4.3.133+ for Portal, appropriate updates for DXP versions) and/or implement output encoding for the definition parameter in the DDMPortlet to prevent script execution.

Recommended fix High confidence

Lifford DXP: 2024.Q1.19+, 2024.Q2.14+, 2024.Q3.14+, 2024.Q4.8+ | Lifford Portal: 7.4.3.133+

1. Identify the currently installed Lifford DXP or Lifford Portal version using the Control Panel or server logs
2. For DXP 2024.Q1.x: Upgrade to version 2024.Q1.19 or later
3. For DXP 2024.Q2.x: Upgrade to version 2024.Q2.14 or later
4. For DXP 2024.Q3.x: Upgrade to version 2024.Q3.14 or later
5. For DXP 2024.Q4.x: Upgrade to version 2024.Q4.8 or later
6. For Lifford Portal 7.4.x: Upgrade to version 7.4.3.133 or later
7. After upgrade, verify the _com_lifera_dynamic_data_mapping_web_portlet_DDMPortlet_definition parameter is properly sanitized
8. Test that the Dynamic Data Mapping portlet functions correctly post-upgrade

Caveat Standard upgrade considerations apply - review Lifford compatibility matrix and test customizations against new version before production deployment

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
Implementation3.0 h
Testing2.0 h
Review / QA1.0 h

8.0 hours of engineering $1,420

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,272.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2025-43757 — 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-43757 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-43757?

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.19 / 2025.Q1.15 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 8 hrs · Moderate

Typical engagement from $1,420

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2025-43757 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