dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43796

HIGH · 7.5 CVSS v3.1 Published 2025-09-12
Fix available
A fix is available. Upgrade to 7.4.3.102 / 2023.Q3.5 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.101, and Liferay DXP 2023.Q3.0 through 2023.Q3.4, 7.4 GA through update 92 and 7.3 GA though update 35 does not limit the number of objects returned from a GraphQL queries, which allows remote attackers to perform denial-of-service (DoS) attacks on the application by executing queries that return 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

Lifteray Portal and DXP fail to impose limits on the number of objects returned from GraphQL queries, enabling attackers to request arbitrarily large result sets that exhaust server resources and cause denial of service.

MitigationImplement pagination limits, query depth restrictions, and result set caps on GraphQL resolvers; apply rate limiting to the GraphQL endpoint; update to patched versions when available.

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:>= 2023.Q3.0, < 2023.Q3.5= 7.3= 7.4
Liferay PortalApplication
Affected:>= 7.4.0, < 7.4.3.102

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 installed Liferay version
    Check the Liferay version by navigating to Control Panel > Configuration > Server Administration > Product Information, or by locating the liferay-version.properties file in the Liferay home directory.
    Affected if The installed version falls within Liferay DXP 2023.Q3.0 through 2023.Q3.4, DXP 7.3, DXP 7.4, or Liferay Portal 7.4.0 through 7.4.3.101.
  2. Verify GraphQL module is enabled
    Navigate to Control Panel > System Settings > Foundation > Module Container and search for GraphQL-related modules, or use the Gogo shell to run 'lb | grep graphql' to list active GraphQL bundles.
    Affected if GraphQL modules are present and in active state.
  3. Inspect GraphQL endpoint accessibility
    Attempt to access the GraphQL endpoint at /o/graphql or /graphql (the exact path depends on your configuration) using a web browser or curl command.
    Affected if The endpoint responds and accepts queries without returning HTTP 403 or requiring disabled status.
  4. Check GraphQL configuration for pagination limits
    Review the GraphQL servlet configuration in the OSGi console or check for com.Liferay.graphql.servlet.GraphQLServlet configuration files; look for settings named 'pageSizeLimit', 'maxResults', or similar result-limiting parameters.
    Affected if No result set size limits, pagination constraints, or query depth restrictions are configured.

You are affected if you run a Liferay version within the affected ranges AND have GraphQL enabled AND have not configured result set limits on GraphQL queries.

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.102 / 2023.Q3.5 or later
Fixed in 7.4.3.1022023.Q3.5
Interim mitigation

Implement pagination limits, query depth restrictions, and result set caps on GraphQL resolvers; apply rate limiting to the GraphQL endpoint; update to patched versions when available.

Recommended fix High confidence

Liferay Portal 7.4.3.102+ or Liferay DXP 2023.Q3.5+

  1. 1. Identify the currently installed Liferay product (Portal or DXP) and exact version from the affected list
  2. 2. For Liferay Portal 7.4.x: Plan upgrade to version 7.4.3.102 or later
  3. 3. For Liferay DXP 2023.Q3.x: Plan upgrade to version 2023.Q3.5 or later
  4. 4. For Liferay DXP 7.4 GA: Plan upgrade past update 92 (e.g., to latest 7.4 update)
  5. 5. For Liferay DXP 7.3 GA: Plan upgrade past update 35 (note: 7.3 is end-of-life, consider migrating to supported version)
  6. 6. Before production upgrade, test the new version in a staging environment to verify the GraphQL query limits are enforced
  7. 7. After upgrade, validate that GraphQL queries function normally with appropriate result limits
Caveat Minor: Upgrading across major versions may introduce deprecation warnings; ensure compatibility testing with custom plugins/modules

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
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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