How severe is CVE-2025-43774?

No CVSS score has been assigned to CVE-2025-43774 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-43774?

CVE-2025-43774 affects the following packages: com.liferay:com.liferay.frontend.taglib.clay (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-43774?

Update com.liferay:com.liferay.frontend.taglib.clay to 15.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-43774 is resolved across your whole dependency graph.

How do I detect CVE-2025-43774 in my Maven dependencies?

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

How do I mitigate CVE-2025-43774 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against CVE-2025-43774?

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

Is CVE-2025-43774 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-43774 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.

When was CVE-2025-43774 published, and has it been updated?

CVE-2025-43774 was published on September 9, 2025 and was last updated on September 10, 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

Not in CISA KEV

CVE-2025-43774 — com.liferay.frontend.tagl…

Fix: liferay/liferay-portal@e15df92

CVE-2025-43774 is a security vulnerability in com.liferay:com.liferay.frontend.taglib.clay. A fix is available for com.liferay:com.liferay.frontend.taglib.clay — see the affected versions and patch details below.

Liferay Portal is vulnerable to XSS attack through its Style Book theme

Published

Sep 9, 2025

Updated

Sep 10, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 10, 2025 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕com.liferay:com.liferay.frontend.taglib.clay

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

Rejected reason: This CVE ID is rejected. The reported vulnerability was found to be present only in a feature that was under development and protected by a beta feature flag. As a result, the issue was not exploitable in the official or public releases within the specified affected ranges, making this a false positive for officially released versions.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay:com.liferay.frontend.taglib.clay`	all versions	15.2.1`com.liferay:com.liferay.frontend.taglib.clay:15.2.1`

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.taglib.clay, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay:com.liferay.frontend.taglib.clay to 15.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-43774 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-43774 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2025-43774. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A reflected cross-site scripting (XSS) vulnerability in the Liferay Portal 7.4.3.132, and Liferay DXP 2025.Q1.0 through 2025.Q1.17 allows a remote authenticated user to inject JavaScript code via Style Book theme name. This malicious payload is then reflected and executed within the user's browser.

O3 Security · Impact-Aware SCA

Is CVE-2025-43774 in your dependencies?

O3 Security finds CVE-2025-43774 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works