How severe is CVE-2024-25610?

CVE-2024-25610 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-25610?

CVE-2024-25610 affects the following packages: com.liferay.portal:release.portal.bom (Maven), com.liferay.portal:release.dxp.bom (Maven), com.liferay.portal:release.dxp.bom (Maven), com.liferay.portal:release.dxp.bom (Maven), com.liferay.portal:com.liferay.portal.web (Maven). Ecosystems affected: Maven.

How do I fix CVE-2024-25610?

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 CVE-2024-25610 is resolved across your whole dependency graph.

How do I detect CVE-2024-25610 in my Maven dependencies?

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.

How do I mitigate CVE-2024-25610 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 CVE-2024-25610 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-25610 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 CVE-2024-25610?

CVE-2024-25610 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th 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 CVE-2024-25610?

CVE-2024-25610 is classified as CWE-1188 (CWE-1188). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-25610 published, and has it been updated?

CVE-2024-25610 was published on February 20, 2024 and was last updated on April 10, 2026. 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

MEDIUM severity

CVE-2024-25610 — release.portal.bom

MEDIUM

CVE-2024-25610 is a medium-severity (CVSS 5.4) 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 asGHSA-vvpf-53qx-cxhh

Published

Feb 20, 2024

Updated

Apr 10, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 4, 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 CVE-2024-25610.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

5 pkgs affected

☕com.liferay.portal:release.portal.bom☕com.liferay.portal:release.dxp.bom☕com.liferay.portal:release.dxp.bom☕com.liferay.portal:release.dxp.bom☕com.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

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay.portal:release.portal.bom`	all versions	7.4.3.13`com.liferay.portal:release.portal.bom:7.4.3.13`
☕Maven	`com.liferay.portal:release.dxp.bom`	≥ 7.4.0&&< 7.4.13.u9	7.4.13.u9`com.liferay.portal:release.dxp.bom:7.4.13.u9`
☕Maven	`com.liferay.portal:release.dxp.bom`	≥ 7.3.0&&< 7.3.10.u4	7.3.10.u4`com.liferay.portal:release.dxp.bom:7.3.10.u4`
☕Maven	`com.liferay.portal:release.dxp.bom`	all versions	7.2.10.fp19`com.liferay.portal:release.dxp.bom:7.2.10.fp19`
☕Maven	`com.liferay.portal:com.liferay.portal.web`	all versions	5.0.96`com.liferay.portal:com.liferay.portal.web:5.0.96`

Affected Products

2 products · 41 configurations

Application

digital experience platformliferay

< 7.2

3 versions

7.27.37.4

Application

liferay portalliferay

< 7.4.3.13

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.portal:release.portal.bom, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 CVE-2024-25610 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

O3 Security · Impact-Aware SCA

Is CVE-2024-25610 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-1188CWE-1188

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

liferay-portal

2.5/10

Code-Review0/10

Maintained10/10

Branch-Protection0/10

Assessed Nov 2, 2026

Timeline

Disclosed

Feb 20, 2024

Last updated

Apr 10, 2026

Identifiers

CVE-2024-25610

GHSA-vvpf-53qx-cxhh

References

Advisoryliferay.dev · cve 2024 25610 Advisorynvd.nist.gov · CVE 2024 25610 Packagegithub.com · liferay portal

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting release.portal.bom are rated as high or higher (top: high).

CVE-2025-62264CVE-2025-62265CVE-2025-62257CVE-2025-62266CVE-2025-62258CVE-2025-62259CVE-2025-62260CVE-2025-62261

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedApr 10, 2026