dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43751

MEDIUM · 5.3 CVSS v3.1 Published 2025-08-22
Fix available
A fix is available. Upgrade to 2024.Q1.15 or later.
See remediation →
62/100
Remediation priority · Elevated
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
User enumeration vulnerability in Liferay Portal 7.4.0 through 7.4.3.132, and Liferay DXP 2024.Q4.0 through 2024.Q4.7, 2024.Q3.0 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.14, 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10 and 7.4 GA through update 92 allows remote attackers to determine if an account exist in the application via the create account page.

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

User enumeration vulnerability in Liferay Portal/DXP allows attackers to determine if an account exists by submitting usernames/email addresses through the create account registration page. The application returns different responses (e.g., error messages, timing differences, or HTTP status codes) depending on whether the submitted credential already exists in the system.

MitigationModify the account creation endpoint to return identical responses (same HTTP status and error message) regardless of whether the submitted username/email already exists, preventing attackers from distinguishing between existing and non-existing accounts. Consider adding rate limiting or CAPTCHA to the endpoint to further impede automated 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
Digital Experience PlatformApplication
Affected:>= 2023.Q3.1, <= 2023.Q3.10>= 2023.q4.0, <= 2023.q4.10>= 2024.Q1.11, < 2024.Q1.15>= 2024.q2.0, <= 2024.q2.13>= 2024.Q3.0, <= 2024.Q3.13>= 2024.q4.0, <= 2024.q4.7= 7.4
Liferay PortalApplication
Affected:>= 7.4.0, <= 7.4.3.132

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Liferize Portal/DXP version
    Locate the version information in the Liferize instance (typically via the control panel, or check the portal-ext.properties file, or the OSGi bundle version information). Compare against affected ranges: DXP 2023.Q3.1 to 2023.Q3.10, 2023.q4.0 to 2023.q4.10, 2024.Q1.11 to 2024.Q1.14, 2024.q2.0 to 2024.q2.13, 2024.Q3.0 to 2024.Q3.13, 2024.q4.0 to 2024.q4.7, and 7.4; Portal 7.4.0 to 7.4.3.132
    Affected if The installed version falls within any of the affected version ranges
  2. Verify create account functionality is enabled
    Confirm whether the user registration/create account feature is accessible on the Liferize instance. Check if the registration endpoint (typically /c/portal/login?p_l_id=xxxxx#sign-in or /web/guest/sign_up) is publicly available without authentication
    Affected if The create account registration page is exposed and accessible to unauthenticated users
  3. Test for user enumeration response differences
    Submit two test requests to the create account endpoint: one with a known-existing username/email (such as admin@localhost or a test account already in the system) and another with a non-existing credential. Compare the HTTP responses, error messages, response timing, and status codes between the two requests
    Affected if The endpoint returns measurably different responses (different error text, different HTTP status codes, or significantly different response times) depending on whether the submitted username/email already exists in the system

A user is affected if the Liferize Portal/DXP version is within the affected ranges AND the create account endpoint is publicly accessible AND the endpoint reveals different responses for existing versus non-existing accounts, allowing an attacker to enumerate valid user credentials.

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 2024.Q1.15 or later
Fixed in 2024.Q1.15
Interim mitigation

Modify the account creation endpoint to return identical responses (same HTTP status and error message) regardless of whether the submitted username/email already exists, preventing attackers from distinguishing between existing and non-existing accounts. Consider adding rate limiting or CAPTCHA to the endpoint to further impede automated enumeration.

Recommended fix High confidence

Upgrade to 7.4.3.133+ for Portal, or 2024.Q1.15+/2024.Q2.14+/2024.Q4.8+ for DXP depending on version line

  1. 1. Identify the currently installed Limerick Portal or DXP version from the control panel or server logs.
  2. 2. Determine the product type (Limerick Portal or DXP) and the current version family (2023.Q3, 2023.Q4, 2024.Q1, 2024.Q2, or 2024.Q4).
  3. 3. For Limerick Portal 7.4.x: Upgrade to version 7.4.3.133 or later (update 93 or higher).
  4. 4. For DXP 2023.Q3.x: Upgrade to version 2023.Q3.11 or later.
  5. 5. For DXP 2023.Q4.x: Upgrade to version 2023.Q4.11 or later.
  6. 6. For DXP 2024.Q1.x: Upgrade to version 2024.Q1.15 or later.
  7. 7. For DXP 2024.Q2.x: Upgrade to version 2024.Q2.14 or later.
  8. 8. For DXP 2024.Q4.x: Upgrade to version 2024.Q4.8 or later.
Caveat Review Limerick upgrade notes for breaking changes between minor versions; major UI or API changes may require testing

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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