dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43801

HIGH · 7.5 CVSS v3.1 Published 2025-09-16
Fix available
A fix is available. Upgrade to 7.3 / 7.4.3.112 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Unchecked input for loop condition vulnerability in XML-RPC in Liferay Portal 7.4.0 through 7.4.3.111, and older unsupported versions, and Liferay DXP 2023.Q4.0, 2023.Q3.1 through 2023.Q3.4, 7.4 GA through update 92, 7.3 GA through update 35, and older unsupported versions allows remote attackers to perform a denial-of-service (DoS) attacks via a crafted XML-RPC request.

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 · moderate confidence

This is an unchecked input vulnerability in Lifer's XML-RPC component where the loop condition is not properly validated. Attackers can send crafted XML-RPC requests with malicious input that controls loop execution, causing excessive resource consumption and leading to denial of service.

MitigationApply vendor-supplied patches or upgrade to a non-vulnerable Lifer version. If XML-RPC is not required, consider disabling the XML-RPC functionality until the patch can be applied.

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.3>= 2023.Q3.0, < 2023.Q3.5= 7.3= 7.4
Liferay PortalApplication
Affected:< 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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 Lifer product and version
    Locate the Lifer installation and determine the exact product (Lifer Digital Experience Platform or Lifer Portal) and version number from the system properties, build info, or admin console.
    Affected if The installed version falls within < 7.3, >= 2023.Q3.0 but < 2023.Q3.5, = 7.3, = 7.4 for DXP, or < 7.4.3.112 for Portal.
  2. Confirm XML-RPC component is present
    Check the Lifer installation for the XML-RPC module or component. This may appear in the module list, plugin inventory, or system information page.
    Affected if XML-RPC functionality is installed or available in the Lifer instance.
  3. Determine if XML-RPC is enabled
    Inspect Lifer's configuration files (such as portal.properties, system.properties, or OSGi config files) and look for XML-RPC related settings or enablement flags.
    Affected if XML-RPC is explicitly enabled or configured to run in the environment.
  4. Check for exposed XML-RPC endpoints
    Review the web server or reverse proxy configuration, and search for XML-RPC endpoint URLs (commonly /xmlrpc or /xmlrpc/* paths) that may be accessible externally.
    Affected if XML-RPC endpoints are exposed and reachable over the network.

A Lifer instance is affected if it runs a vulnerable version (DXP < 7.3, 7.3, 7.4, or >= 2023.Q3.0 < 2023.Q3.5; Portal < 7.4.3.112) AND has XML-RPC enabled and exposed.

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.3 / 7.4.3.112 / 2023.Q3.5 or later
Fixed in 7.37.4.3.1122023.Q3.5
Interim mitigation

Apply vendor-supplied patches or upgrade to a non-vulnerable Lifer version. If XML-RPC is not required, consider disabling the XML-RPC functionality until the patch can be applied.

Recommended fix High confidence

Liferay Portal 7.4.3.112+ or latest stable 7.4.x; DXP 2023.Q3.5+, 2023.Q4.1+, 7.3 update 36+, 7.4 update 93+

  1. 1. Identify the exact current version of Liferay Portal or DXP running in your environment
  2. 2. For Liferay Portal 7.4.x: Upgrade to version 7.4.3.112 or later
  3. 3. For Liferay DXP 2023.Q3.x: Upgrade to version 2023.Q3.5 or later
  4. 4. For Liferay DXP 2023.Q4.x: Upgrade to version 2023.Q4.1 or later
  5. 5. For Liferay DXP 7.3.x: Upgrade to update 36 or later
  6. 6. For Liferay DXP 7.4.x: Upgrade to update 93 or later
  7. 7. After upgrade, verify the XML-RPC service is functioning correctly
  8. 8. Test that the DoS vulnerability is no longer exploitable
Caveat Standard upgrade risks apply - test in staging first; ensure compatibility with custom plugins/themes

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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