dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43799

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-15
Fix available
A fix is available. Upgrade to 7.3 / 7.4.3.112 or later.
See remediation →
74/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
Liferay Portal 7.4.0 through 7.4.3.111, and older unsupported versions, and Liferay DXP 2023.Q4.0, 2023.Q3.1 through 2023.Q3.4, 7.4 GA through update 92 and 7.3 GA through update 35, and older unsupported versions does not limit access to APIs before a user has changed their initial password, which allows remote users to access and edit content via the API.

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

Lifera Portal and DXP versions fail to enforce initial password change requirements for API endpoints, allowing authenticated users with default passwords to bypass normal web UI password change enforcement and directly access REST APIs to read and modify content they should not have access to until resetting their credentials.

MitigationImplement API authentication filters that verify users have completed the initial password change before granting API access, and ensure password change status is checked in all API authorization flows.

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:< 7.3>= 2023.q3.1, < 2023.q3.5= 7.3= 7.4= 2023.q4.0
Liferay PortalApplication
Affected:< 7.4.3.112

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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 installed Liferay Portal version
    Access the Liferay Control Panel, navigate to Configuration > Server Administration > Information, or check the portal-version property in the portal-ext.properties file. Alternatively, review the WAR file version in the application server.
    Affected if The version is Liferay Portal < 7.4.3.112, or Liferay Digital Experience Platform < 7.3, or >= 2023.q3.1 and < 2023.q3.5, or = 7.3, or = 7.4, or = 2023.q4.0
  2. Enumerate user accounts with default passwords
    Log in as an administrator and navigate to Control Panel > Users > Users and Organizations. Review user accounts to identify those that have never changed their initial password or are using default credentials. Check if any service accounts or test accounts retain original passwords.
    Affected if There exist user accounts that have not completed an initial password change since account creation
  3. Test REST API access with default password account
    Using a REST client (curl or Postman), attempt to authenticate to a Liferay REST API endpoint (such as /o/api/v1.0 or /api/jsonws) using credentials for a user account that has a default password. Make the request without performing any password change operation first.
    Affected if The API request succeeds and returns data without requiring the password to be changed, indicating the initial password change is not enforced for API endpoints
  4. Verify password policy configuration
    Navigate to Control Panel > Users > Password Policies. Review the active password policy settings, specifically looking for options related to 'change password on first login' or 'require password reset'. Check if the policy applies to both UI and API authentication flows.
    Affected if The password policy does not enforce initial password change for API-based authentication, or the policy allows API access without password change verification

Your environment is affected if the Liferay version falls within the affected ranges AND you have user accounts with default passwords that can successfully access REST APIs without being forced to change their password first.

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.3 / 7.4.3.112 / 2023.q3.5 or later
Fixed in 7.37.4.3.1122023.q3.5
Interim mitigation

Implement API authentication filters that verify users have completed the initial password change before granting API access, and ensure password change status is checked in all API authorization flows.

Recommended fix High confidence

Lifteray Portal 7.4.3.112+; DXP 2023.Q3.5+

  1. Upgrade Liferay Portal to version 7.4.3.112 or later
  2. If using Liferay DXP 2023.Q3.x, upgrade to version 2023.q3.5 or later
  3. For DXP 7.3 and 7.4, apply the latest available updates that include the security fix (refer to liferay.dev for specific fixed versions)

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
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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