Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
CRITICAL severity

GHSA-vvpf-53qx-cxhh release.portal.bom

CRITICAL

GHSA-vvpf-53qx-cxhh is a critical-severity (CVSS 9) CWE-1188 vulnerability in com.liferay.portal:release.portal.bom. A fix is available for com.liferay.portal:release.portal.bom — see the affected versions and patch details below.

Liferay Portal has a Stored XSS with Blog entries (Insecure defaults)

Also known asCVE-2024-25610
Published
Feb 20, 2024
Updated
Sep 10, 2026
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed
Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • 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-vvpf-53qx-cxhh.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-vvpf-53qx-cxhh plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,238 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

5 pkgs affected
com.liferay.portal:release.portal.bomcom.liferay.portal:release.dxp.bomcom.liferay.portal:release.dxp.bomcom.liferay.portal:release.dxp.bomcom.liferay.portal:com.liferay.portal.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

In Liferay Portal 7.2.0 through 7.4.3.12, and older unsupported versions, and Liferay DXP 7.4 before update 9, 7.3 before update 4, 7.2 before fix pack 19, and older unsupported versions, the default configuration does not sanitize blog entries of JavaScript, which allows remote authenticated users to inject arbitrary web script or HTML (XSS) via a crafted payload injected into a blog entry’s content text field.

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
Mavencom.liferay.portal:release.portal.bomall versions7.4.3.13com.liferay.portal:release.portal.bom:7.4.3.13
Mavencom.liferay.portal:release.dxp.bom7.4.0&&< 7.4.13.u97.4.13.u9com.liferay.portal:release.dxp.bom:7.4.13.u9
Mavencom.liferay.portal:release.dxp.bom7.3.0&&< 7.3.10.u47.3.10.u4com.liferay.portal:release.dxp.bom:7.3.10.u4
Mavencom.liferay.portal:release.dxp.bomall versions7.2.10.fp19com.liferay.portal:release.dxp.bom:7.2.10.fp19
Mavencom.liferay.portal:com.liferay.portal.weball versions5.0.96com.liferay.portal:com.liferay.portal.web:5.0.96

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update com.liferay.portal:release.portal.bom to 7.4.3.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vvpf-53qx-cxhh is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vvpf-53qx-cxhh can be triaged on real exposure rather than presence alone.

Tailored to GHSA-vvpf-53qx-cxhh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In Liferay Portal 7.2.0 through 7.4.3.12, and older unsupported versions, and Liferay DXP 7.4 before update 9, 7.3 before update 4, 7.2 before fix pack 19, and older unsupported versions, the default configuration does not sanitize blog entries of JavaScript, which allows remote authenticated users to inject arbitrary web script or HTML (XSS) via a crafted payload injected into a blog entry’s content text field.
O3 Security · Impact-Aware SCA

Is GHSA-vvpf-53qx-cxhh in your dependencies?

O3 Security finds GHSA-vvpf-53qx-cxhh across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-vvpf-53qx-cxhh: XSS (Critical 9) | O3 Security