dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43797

MEDIUM · 5.4 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 →
60/100
Remediation priority · Elevated
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
In Liferay Portal 7.1.0 through 7.4.3.111, and Liferay DXP 2023.Q4.0, 2023.Q3.1 through 2023.Q3.4, 7.4 GA through update 92, 7.3 GA through update 35, and older unsupported versions, the default membership type of a newly created site is “Open” which allows any registered users to become a member of the site. A remote attacker with site membership can potentially view, add or edit content on the site.

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

In Liferay Portal and DXP, newly created sites have a default membership type of 'Open', which allows any registered user to join without approval. This enables authenticated attackers with site membership to view, add, or edit content on sites they shouldn't have access to.

MitigationChange the default site membership type from 'Open' to 'Restricted' or 'Private' in Liferay's site settings configuration to prevent unauthorized users from joining sites.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 Lifford Portal or DXP version
    Check the Liferax Portal or DXP version by reviewing the server startup logs, the portal-admin Control Panel (Control Panel > Configuration > Server Administration > Product Information), or the portal.properties file. Compare against the affected versions: DXP < 7.3, DXP 2023.q3.1 through < 2023.q3.5, DXP 7.3, DXP 7.4, DXP 2023.q4.0, and Portal < 7.4.3.112.
    Affected if The installed version matches any of the affected version ranges.
  2. Locate default site membership type setting
    Navigate to Control Panel > Configuration > Site Settings > Site Membership > Default User Roles (or equivalent Site Settings configuration depending on exact version). Alternatively, inspect the portal-ext.properties or portal-setup-wizard.properties file for the property controlling default site membership type (such as sites.default.membership.type or similar).
    Affected if The default membership type is configured to 'Open'.
  3. Review existing sites for Open membership
    Navigate to Control Panel > Sites > Sites. For each site, view the Site Membership settings and check if the membership type is set to 'Open'. In the database, query the Site_ table for records where membershipType equals 'Open'.
    Affected if Any site has membership type set to 'Open' and the installed version is affected.

A user is affected if they run an affected Lifford Portal or DXP version and have any site (especially newly created ones) with membership type set to 'Open', which allows unauthorized registered users to join and access content.

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

Change the default site membership type from 'Open' to 'Restricted' or 'Private' in Liferay's site settings configuration to prevent unauthorized users from joining sites.

Recommended fix High confidence

Lifford Portal 7.4.3.112+; DXP 2023.Q3.5+; DXP 7.4 update 93+; DXP 7.3 update 36+

  1. Identify the current Lifeway Portal or DXP version by checking the control panel or bundle information
  2. For Lifford Portal: Upgrade to version 7.4.3.112 or later
  3. For Lifford DXP 2023.Q3.x: Upgrade to version 2023.Q3.5 or later
  4. For Lifford DXP 7.4: Apply update 93 or later (which contains the fix for 7.4 GA through update 92)
  5. For Lifford DXP 7.3: Apply update 36 or later (which contains the fix for 7.3 GA through update 35)
  6. After upgrade, verify that newly created sites no longer default to "Open" membership type by creating a test site and checking the membership settings
Caveat Standard Lifford upgrade precautions apply - review breaking changes in Lifford's upgrade documentation, backup database before upgrading, test in non-production environment first

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

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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