CVE-2024-26268
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 · uneditedUser enumeration vulnerability in Liferay Portal 7.2.0 through 7.4.3.26, and older unsupported versions, and Liferay DXP 7.4 before update 27, 7.3 before update 8, 7.2 before fix pack 20, and older unsupported versions allows remote attackers to determine if an account exist in the application by comparing the request's response time.
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 confidenceUser enumeration vulnerability in Lifford Portal and DXP allows remote attackers to determine if accounts exist by comparing response times from authentication-related endpoints. The timing difference between responses for existing versus non-existing users enables automated account enumeration.
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>= 7.4.0, < 7.4.3.27< 7.2= 7.2= 7.3= 7.4CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 Lifford Portal or DXP versionAccess the Lifford Control Panel or check the portal-ext.properties file for the version property. Alternatively, examine the WAR file manifest or the LIFERAY_VERSION in the system settings.Affected if The installed version is Lifford Portal <= 7.3.7, >= 7.4.0 and < 7.4.3.27, or DXP version 7.2, 7.3, or 7.4 (any update) before the vendor patches were applied.
-
Confirm authentication endpoints are publicly accessibleVerify that web-based authentication endpoints such as /c/portal/login, /web/guest/sign_in, or the default login portlet are exposed to unauthenticated network access without rate limiting or IP restrictions.Affected if Authentication endpoints are reachable from the network without additional access controls and the version is in the affected range.
-
Check for absence of constant-time response mechanismsInspect the authentication configuration in portal-ext.properties or portal-admin settings for parameters controlling response padding, rate limiting, or account enumeration protections.Affected if No rate limiting, account lockout thresholds, or constant-time response delay is configured for failed authentication attempts.
-
Verify user enumeration is observable via timing differencesSend authentication requests for a known non-existent username and a known existing username, then measure and compare response times across multiple attempts. Significant timing variance indicates susceptibility.Affected if Response times differ noticeably between existing and non-existing user accounts, allowing an attacker to infer valid usernames through timing analysis.
A system is affected if it runs a vulnerable Lifford Portal or DXP version (7.2, 7.3, 7.4, or <=7.3.7 to <7.4.3.27) with publicly accessible authentication endpoints that exhibit timing differences that enable user enumeration.
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 · scoped7.27.4.3.27
Apply vendor patches: update to Lifford Portal 7.4.3.27+, DXP 7.4 update 27+, DXP 7.3 update 8+, or DXP 7.2 fix pack 20+. Consider implementing rate limiting or constant-time response mechanisms as defense-in-depth.
Liferay Portal 7.4.3.27+; Liferay Portal 7.3.8+; Liferay DXP 7.4 Update 27+; Liferay DXP 7.3 Update 8+; Liferay DXP 7.2 Fix Pack 20+
- 1. Identify the current Liferay Portal or DXP version by checking the Control Panel or the portal-ext.properties file
- 2. For Liferay Portal 7.4.x: Upgrade to version 7.4.3.27 or later from https://liferaysupport.com/downloads/
- 3. For Liferay Portal 7.3.x: Upgrade to version 7.3.8 or later
- 4. For Liferay DXP 7.4: Apply Update 27 or later via Liferay DXP Package Manager
- 5. For Liferay DXP 7.3: Apply Update 8 or later via Liferay DXP Package Manager
- 6. For Liferay DXP 7.2: Apply Fix Pack 20 or later via Liferay DXP Package Manager
- 7. After upgrading, verify the user enumeration vulnerability is resolved by attempting to enumerate users through response time differences
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26268 — 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-2024-26268 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