CVE-2025-62254
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 · uneditedThe ComboServlet in Liferay Portal 7.4.0 through 7.4.3.111, and older unsupported versions, and Liferay DXP 2023.Q4.0 through 2023.Q4.2, 2023.Q3.1 through 2023.Q3.5, 7.4 GA through update 92, 7.3 GA through update 35, and older unsupported versions does not limit the number or size of the files it will combine, which allows remote attackers to create very large responses that lead to a denial of service attack via the URL query string.
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 confidenceThe ComboServlet in Liferay Portal and DXP lacks validation on the number and size of files specified in the URL query string for combination. Attackers can request extremely large combined responses by specifying large or numerous files, causing resource exhaustion and 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= 7.3= 7.4= 2023.q3.1= 2023.q3.2= 2023.q3.3= 2023.q3.4= 2023.q3.5= 2023.q4.0= 2023.q4.1= 2023.q4.2>= 7.4.0, <= 7.4.3.111CVSS 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 Lifer Portal/DXP versionCheck the portal's version by viewing the release information in the control panel or checking the portal-ext.properties file for the version propertyAffected if The installed version matches 7.3, 7.4, 2023.q3.1-2023.q4.2 for DXP or 7.4.0-7.4.3.111 for Portal
-
Verify ComboServlet is accessibleConfirm the ComboServlet endpoint exists by accessing a URL pattern such as /combo/ or /o/portal/combo with valid file paths in the query stringAffected if The ComboServlet responds to requests and allows file combination via query string parameters
-
Check for lack of request size limitsSend a test request to the ComboServlet with many files or large files in the query string (e.g., ?p=multiple_paths) and observe if the server accepts it without returning an error or enforcing limitsAffected if The server accepts arbitrarily large numbers of files or large combined responses without rejecting them
-
Monitor for unusually large responsesReview server logs or network traffic for ComboServlet requests that return excessively large combined responses, indicating potential exploitationAffected if Large combined responses are observed in logs or traffic that exceed reasonable file combination sizes
You are affected if your Lifer Portal version is 7.4.0 through 7.4.3.111 or your Lifer DXP version is 7.3, 7.4, or any 2023.q3.x or 2023.q4.x release, and the ComboServlet endpoint is accessible and accepts unbounded file combination requests.
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.
From vendor dataImplement server-side limits on the ComboServlet to restrict both the maximum number of files and maximum total size of files that can be combined in a single request.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62254 — 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-62254 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