How severe is GHSA-cv9j-mg9w-v7wm?

No CVSS score has been assigned to GHSA-cv9j-mg9w-v7wm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cv9j-mg9w-v7wm?

GHSA-cv9j-mg9w-v7wm affects the following packages: com.liferay.portal:com.liferay.portal.impl (Maven). Ecosystems affected: Maven.

How do I fix GHSA-cv9j-mg9w-v7wm?

Update com.liferay.portal:com.liferay.portal.impl to 108.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cv9j-mg9w-v7wm is resolved across your whole dependency graph.

How do I detect GHSA-cv9j-mg9w-v7wm in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay.portal:com.liferay.portal.impl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-cv9j-mg9w-v7wm if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-cv9j-mg9w-v7wm actively exploited in the wild?

No public exploit code has been indexed for GHSA-cv9j-mg9w-v7wm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-cv9j-mg9w-v7wm?

GHSA-cv9j-mg9w-v7wm has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 26th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-cv9j-mg9w-v7wm?

GHSA-cv9j-mg9w-v7wm is classified as CWE-201 (CWE-201). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-cv9j-mg9w-v7wm published, and has it been updated?

GHSA-cv9j-mg9w-v7wm was published on August 23, 2025 and was last updated on August 25, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

Liferay Portal JSONWS API endpoint shares sensitive informationGHSA-cv9j-mg9w-v7wm

Fix: liferay/liferay-portal@efdbdbc

GHSA-cv9j-mg9w-v7wm is a CWE-201 vulnerability in com.liferay.portal:com.liferay.portal.impl. A fix is available for com.liferay.portal:com.liferay.portal.impl — see the affected versions and patch details below.

Also known asCVE-2025-43768

Published

Aug 23, 2025

Updated

Aug 25, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-cv9j-mg9w-v7wm.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs26th percentile — riskier than 26% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕com.liferay.portal:com.liferay.portal.impl

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay.portal:com.liferay.portal.impl`	all versions	108.1.1`com.liferay.portal:com.liferay.portal.impl:108.1.1`

Affected Products

2 products · 11 configurations

Application

digital experience platformliferay

≥ 2024.q3.1 && ≤ 2024.q3.13

1 version

7.4

Application

liferay portalliferay

≥ 7.4.0 && < 7.4.3.132

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay.portal:com.liferay.portal.impl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay.portal:com.liferay.portal.impl to 108.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cv9j-mg9w-v7wm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.