dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43768

HIGH · 7.7 CVSS v3.1 Published 2025-08-23
Fix available
A fix is available. Upgrade to 7.4.3.132 / 2024.Q1.16 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable 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
Liferay Portal 7.4.0 through 7.4.3.131, and Liferay DXP 2024.Q4.0 through 2024.Q4.7, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.15 and 7.4 GA through update 92 allows authenticated users without any permissions to access sensitive information of admin users using JSONWS APIs.

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

This is a broken access control vulnerability in Lifer's JSONWS APIs where authenticated users with no permissions can retrieve sensitive information about admin users. The JSONWS web service fails to properly enforce authorization checks, allowing low-privilege authenticated users to access admin user data through API calls.

MitigationApply the vendor patches or upgrade to the fixed Lifer versions (7.4.3.132+, 2024.Q4.8+, etc.). Additionally, review and restrict JSONWS API permissions to ensure only authorized users can access sensitive endpoints.

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:>= 2024.Q1.1, < 2024.Q1.16>= 2024.q2.0, <= 2024.q2.13>= 2024.q3.1, <= 2024.q3.13= 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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/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. Identify Lifer product and version
    Access the Control Panel > Configuration > Server Administration > Version, or check the welcome page footer for version information. Alternatively, examine the WAR file or the bundle's portal-version.properties file.
    Affected if The version falls within: DXP >= 2024.Q1.1 to < 2024.Q1.16, >= 2024.Q2.0 to <= 2024.Q2.13, >= 2024.Q3.1 to <= 2024.Q3.13, or = 7.4; OR Portal >= 7.4.0 to < 7.4.3.132.
  2. Confirm JSONWS API is accessible
    Attempt to access the JSONWS endpoint at /api/jsonws or /c/jsonws on your server. If the endpoint responds (even with an error), it is enabled.
    Affected if The JSONWS API endpoint is reachable and responds to requests.
  3. Verify authentication is enabled for JSONWS
    Check portal-ext.properties or the database portalPreferences table for JSONWS authentication settings. Look for JSONWS security configuration in Control Panel > System Settings > JSON Web Services.
    Affected if JSONWS API allows authenticated user access without proper permission enforcement.
  4. Test for unauthorized admin data access
    Log in as a low-privilege authenticated user (non-admin) and attempt a JSONWS API call to retrieve admin user information, such as calling /user/get-user-by-id with an admin user's ID, or /user/get-users or similar endpoints.
    Affected if A user with no admin permissions can successfully retrieve admin user data through JSONWS API.

You are affected if your Lifer version is within the affected ranges AND the JSONWS API is accessible to authenticated low-privilege users who can retrieve admin user data without proper authorization.

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 7.4.3.132 / 2024.Q1.16 or later
Fixed in 7.4.3.1322024.Q1.16
Interim mitigation

Apply the vendor patches or upgrade to the fixed Lifer versions (7.4.3.132+, 2024.Q4.8+, etc.). Additionally, review and restrict JSONWS API permissions to ensure only authorized users can access sensitive endpoints.

Recommended fix High confidence

LPortal 7.4.3.132; DXP 2024.Q1.16; DXP 2024.Q2.14; DXP 2024.Q3.14; DXP 2024.Q4.8

  1. 1. Identify the exact current version of LPortal or DXP running in your environment
  2. 2. For LPortal 7.4.x users: Upgrade to version 7.4.3.132 or later
  3. 3. For DXP 2024.Q1 users: Upgrade to version 2024.Q1.16 or later
  4. 4. For DXP 2024.Q2 users: Upgrade to version 2024.Q2.14 or later
  5. 5. For DXP 2024.Q3 users: Upgrade to version 2024.Q3.14 or later
  6. 6. For DXP 2024.Q4 users: Upgrade to version 2024.Q4.8 or later
  7. 7. After upgrade, verify that JSONWS APIs properly enforce permission checks for sensitive user data
  8. 8. Review user permissions and API access controls to ensure least-privilege principles are applied
Caveat Standard LPortal/DXP upgrade considerations apply - review breaking changes in release notes for your specific version jump

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

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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