Skip to content

GHSA-43xf-59vr-g4f2 CVE-2025-43799

Liferay Portal Uses Default Password

Medium Maven
Severity
0.0 / 10
Medium · CVSS 4.0
Exploit chance (EPSS)
0.26%
Chance of exploitation in the next 30 days. Higher than 17.94% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-1393 Use of Default Password
Fix
7.4.3.112
Upgrade com.liferay.portal:release.portal.bom to this version or later

Description

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.

Affected versions

Maven

PackageVulnerableFixed in
com.liferay.portal:release.portal.bom
>= 7.4.0, < 7.4.3.112
7.4.3.112

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

com.liferay.portal:release.portal.bom Maven → 7.4.3.112

maven
<dependency><groupId>com.liferay.portal</groupId><artifactId>release.portal.bom</artifactId><version>7.4.3.112</version></dependency>
gradle
implementation("com.liferay.portal:release.portal.bom:7.4.3.112")

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
None
User interaction
None
Confidentiality (vulnerable system)
Low
Integrity (vulnerable system)
Low
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

CVSS 3.1 6.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Weakness

CWE-1393: Use of Default Password

The product uses default passwords for potentially critical functionality.

How to prevent it
  • Requirements: Prohibit use of default, hard-coded, or other values that do not vary for each installation of the product - especially for separate organizations.
  • Documentation: Ensure that product documentation clearly emphasizes the presence of default passwords and provides steps for the administrator to change them.
  • Architecture and Design: Force the administrator to change the credential upon installation.
  • Installation, Operation: The product administrator could change the defaults upon installation or during operation.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-2j97-4jmq-c4xf
Liferay Portal Vulnerable to Reflected XSS via the selectedLanguageId Parameter
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-56jv-4ww3-65mw
Liferay Portal is vulnerable to XSS in the Blogs widget
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-f5vh-4rj2-w8r8
Liferay Portal is vulnerable to DNS rebinding attacks
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-8hw3-ghwv-crfh
Liferay Portal vulnerable to password enumeration
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-gv7w-jh8g-vr73
Liferay Portal Does Not Limit Access to APIs Before Email Verification
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-gh4w-8qgq-8w9r
Liferay Portal Vulnerable to CSRF in Headless APIs
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-xcj6-xpjg-c4xr
Liferay Portal Stores Password Reset Tokens in Plain Text
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-vgqx-447m-wvcj
Liferay Portal Vulnerable to DoS via Crafted Headless API Request
High Also affects com.liferay.portal:release.portal.bom
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor