GHSA-9fcg-wrp8-qhr4 CVE-2025-2565
Liferay Portal and Liferay DXP Reveals Data via Forms
- Severity
- 0.0 / 10
- Medium · CVSS 4.0
- Exploit chance (EPSS)
- 0.27%
- Chance of exploitation in the next 30 days. Higher than 19.73% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-201 Insertion of Sensitive Information Into Sent Data
- Fix
- Available
- 2 packages have a fixed version
Description
The data exposure vulnerability in Liferay Portal 7.4.0 through 7.4.3.126, and Liferay DXP 2024.Q3.0, 2024.Q2.0 through 2024.Q2.12, 2024.Q1.1 through 2024.Q1.12, 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10, 7.4 GA through update 92 allows an unauthorized user to obtain entry data from forms.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| com.liferay.portal:release.dxp.bom | >= 2024.Q3.0, < 2024.Q3.1 |
2024.Q3.1 |
| com.liferay.portal:release.dxp.bom | >= 2024.Q2.0, <= 2024.Q2.12 |
No fix yet |
| com.liferay.portal:release.dxp.bom | >= 2024.Q1.1, < 2024.Q1.13 |
2024.Q1.13 |
| com.liferay.portal:release.dxp.bom | >= 2023.Q4.0, <= 2023.Q4.10 |
No fix yet |
| com.liferay.portal:release.dxp.bom | >= 2023.Q3.1, <= 2023.Q3.10 |
No fix yet |
| com.liferay.portal:release.portal.bom | >= 7.4.0, < 7.4.3.129 |
7.4.3.129 |
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.dxp.bom Maven → 2024.Q3.1
- maven
<dependency><groupId>com.liferay.portal</groupId><artifactId>release.dxp.bom</artifactId><version>2024.Q3.1</version></dependency>- gradle
implementation("com.liferay.portal:release.dxp.bom:2024.Q3.1")
com.liferay.portal:release.portal.bom Maven → 7.4.3.129
- maven
<dependency><groupId>com.liferay.portal</groupId><artifactId>release.portal.bom</artifactId><version>7.4.3.129</version></dependency>- gradle
implementation("com.liferay.portal:release.portal.bom:7.4.3.129")
Severity breakdown
CVSS 4.0 0.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- Attack vector
- Network
- Attack complexity
- Low
- Attack requirements
- None
- Privileges required
- None
- User interaction
- Active
- Confidentiality (vulnerable system)
- Low
- Integrity (vulnerable system)
- None
- Availability (vulnerable system)
- None
- Confidentiality (subsequent systems)
- Low
- Integrity (subsequent systems)
- None
- Availability (subsequent systems)
- None
- Exploit maturity
- Not defined
- Scope
- X
CVSS 3.1 4.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Weakness
CWE-201: Insertion of Sensitive Information Into Sent Data
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
How to prevent it
- Requirements: Specify which data in the software should be regarded as sensitive. Consider which types of users should have access to which types of data.
- Implementation: Ensure that any possibly sensitive data specified in the requirements is verified with designers to ensure that it is either a calculated risk or mitigated elsewhere. Any information that is not necessary to the functionality should be removed in order to lower both the overhead and the possibility of security sensitive data being sent.
- System Configuration: Setup default error messages so that unexpected errors do not disclose sensitive information.
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why 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 |
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