How severe is GHSA-3h7r-4xxj-3mfm?

No CVSS score has been assigned to GHSA-3h7r-4xxj-3mfm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3h7r-4xxj-3mfm?

GHSA-3h7r-4xxj-3mfm affects the following packages: com.liferay:com.liferay.frontend.editor.ckeditor.web (Maven), com.liferay:com.liferay.frontend.js.dependencies.web (Maven), liferay-ckeditor (npm). Ecosystems affected: Maven, npm.

How do I fix GHSA-3h7r-4xxj-3mfm?

Update com.liferay:com.liferay.frontend.editor.ckeditor.web to 5.0.107 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3h7r-4xxj-3mfm is resolved across your whole dependency graph.

How do I detect GHSA-3h7r-4xxj-3mfm in my Maven, npm dependencies?

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

How do I mitigate GHSA-3h7r-4xxj-3mfm if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-3h7r-4xxj-3mfm actively exploited in the wild?

No public exploit code has been indexed for GHSA-3h7r-4xxj-3mfm 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-3h7r-4xxj-3mfm?

GHSA-3h7r-4xxj-3mfm has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 9th 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-3h7r-4xxj-3mfm?

GHSA-3h7r-4xxj-3mfm is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-3h7r-4xxj-3mfm published, and has it been updated?

GHSA-3h7r-4xxj-3mfm 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📦 npm

Not in CISA KEV

Liferay Portal Reflected XSS in CKeditor 4.21.0 endpointGHSA-3h7r-4xxj-3mfm

Fix: liferay/liferay-portal@4b638ee

GHSA-3h7r-4xxj-3mfm is a Cross-site Scripting (XSS) vulnerability in com.liferay:com.liferay.frontend.editor.ckeditor.web. A fix is available for com.liferay:com.liferay.frontend.editor.ckeditor.web — see the affected versions and patch details below.

Also known asCVE-2025-43761

Published

Aug 22, 2025

Updated

Aug 25, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
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-3h7r-4xxj-3mfm.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs9th percentile — riskier than 9% of all scored CVEsHighest risk

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

Real-World Exposure

3 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

2other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

liferay-ckeditornpm

10Kdownloads / week

Description

A reflected cross-site scripting (XSS) vulnerability in the Liferay Portal 7.4.0 through 7.4.3.131, and Liferay DXP 2024.Q4.0 through 2024.Q4.4, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.12 and 7.4 GA through update 92 allows an remote non-authenticated attacker to inject JavaScript into the frontend-editor-ckeditor-web/ckeditor/samples/old/ajax.html path

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay:com.liferay.frontend.editor.ckeditor.web`	all versions	5.0.107`com.liferay:com.liferay.frontend.editor.ckeditor.web:5.0.107`
☕Maven	`com.liferay:com.liferay.frontend.js.dependencies.web`	all versions	1.0.25`com.liferay:com.liferay.frontend.js.dependencies.web:1.0.25`
📦npm	`liferay-ckeditor`	all versions	4.21.0-liferay.10`npm install liferay-ckeditor@4.21.0-liferay.10`

Affected Products

2 products · 98 configurations

Application

digital experience platformliferay

≥ 2024.Q4.0 && ≤ 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:com.liferay.frontend.editor.ckeditor.web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay:com.liferay.frontend.editor.ckeditor.web to 5.0.107 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3h7r-4xxj-3mfm is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.