Digital Experience PlatformApplication · Liferay

CVE-2025-4388

MEDIUM · 6.1 CVSS v3.1 Published 2025-05-06

Fix available

A fix is available. Upgrade to 7.4.3.132 / 2024.Q1.13 or later.

See remediation →

68/100

Remediation priority · Elevated

Remotely reachable No privileges

Official description

NVD · unedited

A reflected cross-site scripting (XSS) vulnerability in the Liferay Portal 7.4.0 through 7.4.3.131, and Liferay DXP 2024.Q4.0 through 2024.Q4.5, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.12, 7.4 GA through update 92 allows an remote non-authenticated attacker to inject JavaScript into the modules/apps/marketplace/marketplace-app-manager-web.

Technical summary

dbcve analysis · moderate confidence

Reflected cross-site scripting (XSS) vulnerability in Lifer L Portal and DXP's marketplace-app-manager-web module allows unauthenticated remote attackers to inject arbitrary JavaScript via unspecified parameters in the affected URL path.

MitigationApply vendor-supplied patches or upgrade to a Lifer L version beyond the vulnerable ranges (7.4.3.132+ or corresponding DXP updates) to remediate the XSS in the marketplace-app-manager-web.

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.13>= 2024.q2.0, < 2024.q4.6= 7.4

Liferay PortalApplication

Affected:>= 7.4.0, < 7.4.3.132

CVSS breakdown

From the vector

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

CVSS:3.1/AV:N/AC:L/PR:N/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 your Lifer Portal version

Locate the Lifer portal-ext.properties or portal.properties file (typically in the Lifer home directory or WEB-INF/classes). Look for the 'iver.version' property, or check the Lifer login page footer which displays the running version. Alternatively, inspect the MANIFEST.MF file in the core portal JAR (portal-impl.jar) for the Bundle-Version attribute.

Affected if The version is 7.4.0 through 7.4.3.131 (inclusive), or the version string starts with 7.4 but is below 7.4.3.132.
Check your Lifer DXP version

In the Lifer DXP digital experience platform, access the Control Panel > Configuration > Server Administration > Product Information, or check the osgi/state directory for bundle version files. The version typically appears as a quarterly release such as 2024.Q1.x, 2024.Q2.x, or 2024.Q4.x.

Affected if The DXP version is 2024.Q1.1 through 2024.Q1.12 (inclusive), 2024.Q2.0 through 2024.Q4.5 (inclusive), or specifically 7.4.
Verify marketplace-app-manager-web module is deployed

Access the Lifer Control Panel > Configuration > System Settings > Gogo Shell. Execute the command 'lb marketplace-app-manager-web' or 'lb | grep marketplace' to list the marketplace-related bundles and confirm the module is loaded in the OSGi runtime.

Affected if The marketplace-app-manager-web bundle appears in the active bundles list with a state of ACTIVE.
Inspect URL handling for the affected path

Review the web server access logs or proxy logs for requests to paths containing 'marketplace-app-manager-web' or marketplace-related endpoints. Look for any URL parameters that may be reflected in the response without proper encoding.

Affected if The server responds with pages containing URL parameter values from requests targeting the marketplace-app-manager-web module path.

You are affected if your Lifer Portal is version 7.4.0-7.4.3.131, or your Lifer DXP is version 2024.Q1.1-2024.Q1.12, 2024.Q2.0-2024.Q4.5, or 7.4, AND the marketplace-app-manager-web module is deployed and accessible.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 7.4.3.132 / 2024.Q1.13 / 2024.q4.6 or later

Fixed in 7.4.3.1322024.Q1.132024.q4.6

Interim mitigation

Apply vendor-supplied patches or upgrade to a Lifer L version beyond the vulnerable ranges (7.4.3.132+ or corresponding DXP updates) to remediate the XSS in the marketplace-app-manager-web.

Recommended fix High confidence

Upgrade to the appropriate fixed version: Liferay Portal 7.4.3.132+; DXP 2024.Q1.13+; DXP 2024.Q2.13+; DXP 2024.Q4.6+

1. Identify the exact Liferay product and version currently running (Portal or DXP, and the specific version number from the affected ranges)
2. For Liferay Portal 7.4.x: upgrade to version 7.4.3.132 or later
3. For Liferay DXP 2024.Q1.x: upgrade to version 2024.Q1.13 or later
4. For Liferay DXP 2024.Q2.x: upgrade to version 2024.Q2.13 or later
5. For Liferay DXP 2024.Q4.x: upgrade to version 2024.Q4.6 or later
6. After upgrade, verify the marketplace-app-manager-web module is functioning correctly and the XSS vulnerability is resolved by testing that special characters in URLs are properly escaped

Caveat Review Liferay release notes for the target version to check for any breaking changes or required migration steps; minor version upgrades typically have low risk

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
Implementation4.0 h
Testing4.0 h
Review / QA2.0 h

12.0 hours of engineering $2,080

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Notes0 Guidelines

Know something about CVE-2025-4388?

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 7.4.3.132 / 2024.Q1.13 or later

Severity 6.1 Medium

Exploit likelihood EPSS, next 30 days 3.8%

Affects: Digital Experience Platform

Remediation

Need this fixed?

Fix this in Digital Experience Platform 12 hrs · Moderate

Typical engagement from $2,080

Get a fix See the full breakdown ↓

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