CVE-2025-3602
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 · uneditedLiferay Portal 7.4.0 through 7.4.3.97, and Liferay DXP 2023.Q3.1 through 2023.Q3.2, 7.4 GA through update 92, 7.3 GA through update 35, and 7.2 fix pack 8 through fix pack 20 does not limit the depth of a GraphQL queries, which allows remote attackers to perform denial-of-service (DoS) attacks on the application by executing complex queries.
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 confidenceLaravel Portal and DXP versions 7.2-7.4.3.97 contain a vulnerability in the GraphQL API where query depth is not limited, allowing attackers to craft deeply nested queries that consume excessive server resources and cause denial of service.
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>= 2023.q3.1, <= 2023.q3.2= 7.2= 7.3= 7.4>= 7.4.0, <= 7.4.3.97CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Liferay Portal or DXP versionCheck the product version through the Liferay Control Panel (Control Panel > Configuration > System Information) or by examining the portal-ext.properties file for the version property. Alternatively, access the Liferay JSON web services or examine the WAR file manifest.Affected if The installed version falls within >= 7.4.0 to <= 7.4.3.97 for Portal, or matches 7.2, 7.3, 7.4, or 2023.q3.1 to 2023.q3.2 for DXP.
-
Verify GraphQL API module is enabledCheck if the GraphQL module is deployed and active. In Liferay OSGi console, run 'ls | grep graphql' or check the Gogo shell with 'lb -s | grep -i graphql'. Also verify the GraphQL servlet is registered at /graphql endpoint.Affected if The GraphQL module com.liferay.portal.workflow.graphql or similar is loaded and the /graphql endpoint responds to HTTP requests.
-
Confirm no query depth limiting is configuredExamine the portal-ext.properties or portal-setup-wizard.properties for GraphQL-related settings. Search for properties containing 'graphql', 'depth', or 'query' keywords. Check if maxQueryDepth or similar limiting configuration exists.Affected if No max query depth limit is set in configuration files, or the GraphQL schema allows unlimited depth without depth validation in the resolver layer.
-
Test GraphQL endpoint for depth vulnerabilitySend a crafted GraphQL query with excessive nested fragments or queries (e.g., '{ user { groups { sites { ... } } } }' repeated 20+ levels deep) to the /graphql endpoint and observe server response time and resource consumption.Affected if The server accepts deeply nested queries without returning a depth limit error and shows increased response time or memory usage proportional to query depth.
A user is affected if they run a Liferay Portal 7.4.0-7.4.3.97 or DXP 7.2/7.3/7.4/2023.q3.1-2023.q3.2 instance with the GraphQL API enabled and without query depth limiting configured.
Generated from the published advisory. Verify against your own configuration.
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 · scopedImplement GraphQL query depth limiting on the affected endpoints to restrict the maximum nesting level of queries, and consider adding query complexity analysis and rate limiting as additional defenses.
Lifera Portal 7.4.3.98+ / DXP 2023.Q3.3+ / DXP 7.4 update 93+ / DXP 7.3 update 36+ / DXP 7.2 fix pack 21+
- 1. Identify your current Liferay Portal or DXP version using the Admin Panel or system properties
- 2. For Liferay Portal 7.4.x: Upgrade to version 7.4.3.98 or later
- 3. For Liferay DXP 2023.Q3.x: Upgrade to version 2023.Q3.3 or later
- 4. For Liferay DXP 7.4: Apply update 93 or later
- 5. For Learable DXP 7.3: Apply update 36 or later
- 6. For Learable DXP 7.2: Apply fix pack 21 or later
- 7. After upgrade, verify GraphQL endpoint responds normally and test with complex nested queries to confirm depth is now limited
- 8. Review release notes for any additional security fixes included in the target version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3602 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-3602 in production — separate from our analysis above.
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.
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.
- 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