How severe is GHSA-q8fj-76q7-4p7h?

No CVSS score has been assigned to GHSA-q8fj-76q7-4p7h yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q8fj-76q7-4p7h?

GHSA-q8fj-76q7-4p7h affects the following packages: com.liferay:com.liferay.flags.web (Maven). Ecosystems affected: Maven.

How do I fix GHSA-q8fj-76q7-4p7h?

Update com.liferay:com.liferay.flags.web to 6.0.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q8fj-76q7-4p7h is resolved across your whole dependency graph.

How do I detect GHSA-q8fj-76q7-4p7h in my Maven dependencies?

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

How do I mitigate GHSA-q8fj-76q7-4p7h 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-q8fj-76q7-4p7h actively exploited in the wild?

No public exploit code has been indexed for GHSA-q8fj-76q7-4p7h 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-q8fj-76q7-4p7h?

GHSA-q8fj-76q7-4p7h has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 12th 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-q8fj-76q7-4p7h?

GHSA-q8fj-76q7-4p7h 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-q8fj-76q7-4p7h published, and has it been updated?

GHSA-q8fj-76q7-4p7h was published on October 8, 2025 and was last updated on October 9, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Liferay Portal Notifications Widget has multiple XSS…

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-q8fj-76q7-4p7h.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs12th percentile — riskier than 12% 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:com.liferay.flags.web

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

Multiple cross-site scripting (XSS) vulnerabilities in the Notifications widget in Liferay Portal 7.4.3.102 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.5 and 2023.Q3.1 through 2023.Q3.10 allow remote attackers to inject arbitrary web script or HTML via a crafted payload injected into (1) a user’s “First Name” text field, (2) a user’s “Middle Name” text field, (3) a user’s “Last Name” text field, (4) the “Other Reason” text field when flagging content, or (5) the name of the flagged content.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay:com.liferay.flags.web`	≥ 6.0.23&&< 6.0.24	6.0.24`com.liferay:com.liferay.flags.web:6.0.24`

Affected Products

2 products · 3 configurations

Application

digital experience platformliferay

≥ 2023.q4.0 && < 2023.q4.6

range

Application

liferay portalliferay

≥ 7.4.3.102 && < 7.4.3.112

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.flags.web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay:com.liferay.flags.web to 6.0.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q8fj-76q7-4p7h 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.

Frequently Asked Questions

Multiple cross-site scripting (XSS) vulnerabilities in the Notifications widget in Liferay Portal 7.4.3.102 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.5 and 2023.Q3.1 through 2023.Q3.10 allow remote attackers to inject arbitrary web script or HTML via a crafted payload injected into (1) a user’s “First Name” text field, (2) a user’s “Middle Name” text field, (3) a user’s “Last Name” text field, (4) the “Other Reason” text field when flagging content, or (5) the name of the flagged content.

O3 Security · Impact-Aware SCA

Is GHSA-q8fj-76q7-4p7h in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

Liferay Portal Notifications Widget has multiple XSS vulnerabilities through various text fieldsGHSA-q8fj-76q7-4p7h