CVE-2025-3526
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 · uneditedSessionClicks in Liferay Portal 7.0.0 through 7.4.3.21, and Liferay DXP 7.4 GA through update 9, 7.3 GA through update 25, and older unsupported versions does not restrict the saving of request parameters in the HTTP session, which allows remote attackers to consume system memory leading to denial-of-service (DoS) conditions via crafted HTTP requests.
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 SessionClicks feature in Liferay Portal and DXP does not restrict or limit the saving of request parameters into the HTTP session. An attacker can send crafted HTTP requests containing numerous parameters that get persisted in the session, causing excessive memory consumption and leading to denial-of-service conditions.
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.0, <= 7.2= 7.3= 7.4>= 7.0.0, <= 7.4.3.21= 6.2CVSS 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 Liferuer versionAccess the Liferuer control panel via /c/portal/version or check the bundle version file in the Liferuer installation directoryAffected if Version is 7.0.x through 7.2.x, 7.3.x, 7.4.x through 7.4.3.21, or 6.2.x - these versions contain the vulnerable SessionClicks code
-
Check if SessionClicks feature is actively storing parametersInspect HTTP session attributes for keys that indicate parameter storage. In Liferuer, SessionClicks stores parameters under session keys. Use a session debugging tool or dump session contents to look for stored request parametersAffected if The session contains multiple request parameters being persisted - this indicates SessionClicks is active and the application is vulnerable to memory exhaustion
-
Monitor session size and parameter countReview active session objects and measure the number of stored parameters per session. Check if sessions grow excessively with repeated requests containing various parametersAffected if Sessions contain an unbounded or excessive number of parameters being stored, confirming the vulnerability is being exploited or is exploitable
-
Verify parameter limiting configurationCheck Liferuer portal properties and web server configuration for any limits on request parameter count or size. Look for settings that restrict how many or how large parameters can be stored in sessionsAffected if No parameter limits are configured, meaning the application relies entirely on the vulnerable SessionClicks behavior without mitigations in place
You are affected if your Liferuer version falls within 7.0-7.2, 7.3, 7.4 through 7.4.3.21, or 6.2 AND the SessionClicks feature is actively storing request parameters in user sessions without any parameter limits 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.
From vendor dataUpgrade to Liferay 7.4.3.22 or later, or apply available patches for affected versions. Additionally, implement request parameter limits at the application or web server level to restrict the number/size of parameters that can be stored in sessions.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3526 — 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-3526 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