How severe is GHSA-84pp-qr92-95c9?

No CVSS score has been assigned to GHSA-84pp-qr92-95c9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-84pp-qr92-95c9?

GHSA-84pp-qr92-95c9 affects the following packages: com.liferay:com.liferay.dynamic.data.mapping.form.web (Maven), com.liferay:com.liferay.dynamic.data.mapping.form.field.type (Maven). Ecosystems affected: Maven.

How do I fix GHSA-84pp-qr92-95c9?

Update com.liferay:com.liferay.dynamic.data.mapping.form.web to 4.0.180 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-84pp-qr92-95c9 is resolved across your whole dependency graph.

How do I detect GHSA-84pp-qr92-95c9 in my Maven dependencies?

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

How do I mitigate GHSA-84pp-qr92-95c9 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-84pp-qr92-95c9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-84pp-qr92-95c9 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-84pp-qr92-95c9?

GHSA-84pp-qr92-95c9 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 30th 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-84pp-qr92-95c9?

GHSA-84pp-qr92-95c9 is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-84pp-qr92-95c9 published, and has it been updated?

GHSA-84pp-qr92-95c9 was published on August 22, 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

GHSA-84pp-qr92-95c9 — com.liferay.dynamic.data.…

Fix: liferay/liferay-portal@9d32b08

GHSA-84pp-qr92-95c9 is a CWE-770 vulnerability in com.liferay:com.liferay.dynamic.data.mapping.form.web. A fix is available for com.liferay:com.liferay.dynamic.data.mapping.form.web — see the affected versions and patch details below.

Liferay Portal users can upload an unlimited amount of files

Also known asCVE-2025-43762

Published

Aug 22, 2025

Updated

Aug 25, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 26, 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-84pp-qr92-95c9.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs30th percentile — riskier than 30% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

☕com.liferay:com.liferay.dynamic.data.mapping.form.web☕com.liferay:com.liferay.dynamic.data.mapping.form.field.type

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.132, and Liferay DXP 2025.Q1.0 through 2025.Q1.1, 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.14 and 7.4 GA through update 92 allow users to upload an unlimited amount of files through the forms, the files are stored in the document_library allowing an attacker to cause a potential DDoS.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay:com.liferay.dynamic.data.mapping.form.web`	all versions	4.0.180`com.liferay:com.liferay.dynamic.data.mapping.form.web:4.0.180`
☕Maven	`com.liferay:com.liferay.dynamic.data.mapping.form.field.type`	all versions	6.0.187`com.liferay:com.liferay.dynamic.data.mapping.form.field.type:6.0.187`

Affected Products

2 products · 99 configurations

Application

digital experience platformliferay

≥ 2025.Q1.0 && ≤ 2024.q4.7

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:com.liferay.dynamic.data.mapping.form.web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay:com.liferay.dynamic.data.mapping.form.web to 4.0.180 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-84pp-qr92-95c9 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.