How severe is GHSA-r367-q549-pgr5?

No CVSS score has been assigned to GHSA-r367-q549-pgr5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r367-q549-pgr5?

GHSA-r367-q549-pgr5 affects the following packages: com.liferay:com.liferay.layout.taglib (Maven). Ecosystems affected: Maven.

How do I fix GHSA-r367-q549-pgr5?

Update com.liferay:com.liferay.layout.taglib to 16.1.32 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r367-q549-pgr5 is resolved across your whole dependency graph.

How do I detect GHSA-r367-q549-pgr5 in my Maven dependencies?

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

How do I mitigate GHSA-r367-q549-pgr5 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-r367-q549-pgr5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-r367-q549-pgr5 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-r367-q549-pgr5?

GHSA-r367-q549-pgr5 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-r367-q549-pgr5?

GHSA-r367-q549-pgr5 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-r367-q549-pgr5 published, and has it been updated?

GHSA-r367-q549-pgr5 was published on August 22, 2025 and was last updated on August 22, 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 Reflected Cross-Site Scripting Vulnerability…

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-r367-q549-pgr5.

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.layout.taglib

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

A reflected cross-site scripting (XSS) vulnerability in the Liferay Portal 7.4.3.32 through 7.4.3.132, and Liferay DXP 2025.Q1.0 through 2025.Q1.7, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.1 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.16 and 7.4 update 32 through update 92 allows an remote authenticated user to inject JavaScript into the embedded message field from the form container.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay:com.liferay.layout.taglib`	all versions	16.1.32`com.liferay:com.liferay.layout.taglib:16.1.32`

Affected Products

2 products · 67 configurations

Application

digital experience platformliferay

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

1 version

7.4

Application

liferay portalliferay

≥ 7.4.3.32 && ≤ 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.layout.taglib, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay:com.liferay.layout.taglib to 16.1.32 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r367-q549-pgr5 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

A reflected cross-site scripting (XSS) vulnerability in the Liferay Portal 7.4.3.32 through 7.4.3.132, and Liferay DXP 2025.Q1.0 through 2025.Q1.7, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.1 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.16 and 7.4 update 32 through update 92 allows an remote authenticated user to inject JavaScript into the embedded message field from the form container.

O3 Security · Impact-Aware SCA

Is GHSA-r367-q549-pgr5 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

Liferay Portal Reflected Cross-Site Scripting Vulnerability via Form ContainerGHSA-r367-q549-pgr5