dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-62260

HIGH · 7.5 CVSS v3.1 Published 2025-10-27
Fix available
A fix is available. Upgrade to 7.4.3.99 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
Liferay Portal 7.4.0 through 7.4.3.99, and Liferay DXP 2023.Q3.1 through 2023.Q3.4, 7.4 GA through update 92, 7.3 GA through update 35, and older unsupported versions does not limit the number of objects returned from Headless API requests, which allows remote attackers to perform denial-of-service (DoS) attacks on the application by executing a request that returns a large number of objects.

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

Lifera Portal and DXP Headless API does not implement limits or pagination on object collections returned by API requests, allowing remote attackers to trigger responses containing extremely large datasets that exhaust server resources and cause denial of service.

MitigationApply vendor-supplied patches (Lifera updates 93 for 7.4.x, 36 for 7.3.x, Q3.5 for 2023.Q3) to enforce API response limits, or implement pagination controls on Headless API endpoints.

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= 7.4= 2023.q3.1= 2023.q3.2= 2023.q3.3= 2023.q3.4
Liferay PortalApplication
Affected:>= 7.4.0, < 7.4.3.99

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 Portal/DXP version
    Check the product version in the Lifer control panel (Control Panel > Configuration > System Information) or check the portal-ext.properties file for the version property
    Affected if Version matches 7.3.x, 7.4.0-7.4.3.98, or 2023.q3.x (any version before Q3.5)
  2. Verify Headless API is enabled
    Check if the com.fasterxml.jackson.jaxrs.json property is enabled in the system or inspect the /o/api endpoint accessible without authentication
    Affected if Headless API endpoints are publicly accessible and no authentication is required for API collection queries
  3. Confirm no pagination limits are configured
    Inspect the Headless API configuration files (especially com.lifer.portal.headless.* properties in portal-ext.properties or OSGi config) for pagination settings like "pageSize" or "maxResults"
    Affected if No pagination or limit configuration exists for API collection endpoints
  4. Test API response size behavior
    Make a test request to a Headless API collection endpoint (such as /o/c/yourentity) without pagination parameters and observe if the full dataset is returned without limit
    Affected if The API returns all records in a single response without enforcing a maximum page size or result limit

Your environment is affected if you run any of the listed Lifer versions and the Headless API is accessible without pagination controls configured, allowing unrestricted collection responses that could exhaust server resources.

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.99 or later
Fixed in 7.4.3.99
Interim mitigation

Apply vendor-supplied patches (Lifera updates 93 for 7.4.x, 36 for 7.3.x, Q3.5 for 2023.Q3) to enforce API response limits, or implement pagination controls on Headless API endpoints.

Recommended fix High confidence

Lifera Portal 7.4.3.99+ or latest 7.4.x; Lifera DXP 7.4 update 93+, 7.3 update 36+, or 2023.Q4+

  1. 1. Identify your current Limerick Portal or DXP version by checking the Limerick Control Panel > Configuration > Server Administration > Version
  2. 2. For Limerick Portal 7.4.x users: Upgrade to Limerick Portal 7.4.3.99 or later (recommended: latest 7.4.x stable release)
  3. 3. For Limerick DXP 7.4 users: Apply Limerick DXP 7.4 GA update 93 or later
  4. 4. For Limerick DXP 7.3 users: Apply Limerick DXP 7.3 GA update 36 or later
  5. 5. For Limerick DXP 2023.Q3.x users: Upgrade to Limerick DXP 2023.Q4 or later
  6. 6. After upgrade, verify Headless API endpoints function correctly and confirm pagination is enforced
  7. 7. Test with a large dataset to confirm DoS mitigation is effective
Caveat Minor: Upgrades may include other feature changes; test thoroughly in staging environment 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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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