# CVE-2025-43774: Liferay Portal is vulnerable to XSS attack through its Style Book theme


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 9 Sep 2025
- **Updated:** 18 Sep 2025
- **Also known as:** GHSA-qgj5-4qvg-2f8c

## What is CVE-2025-43774?

CVE-2025-43774 is a vulnerability in com.liferay:com.liferay.frontend.taglib.clay, published on 9 Sep 2025. 

### Official description

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.

## Which versions are affected by CVE-2025-43774?

2 open source packages ship an affected version, including com.liferay:com.liferay.frontend.taglib.clay.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.liferay:com.liferay.frontend.taglib.clay` | Maven | All versions | 15.2.1 |
| `com.liferay:com.liferay.frontend.taglib.clay` | Maven | All versions | 15.2.1 |

## How do I fix CVE-2025-43774?

Upgrade com.liferay:com.liferay.frontend.taglib.clay to 15.2.1 or later.

## Is CVE-2025-43774 being exploited?

There is no known exploitation of CVE-2025-43774 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-43774 and fix it if it is affected.

What it is: CVE-2025-43774 is a vulnerability in com.liferay:com.liferay.frontend.taglib.clay, published on 9 Sep 2025. 
Exploitation: There is no known exploitation of CVE-2025-43774 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.liferay:com.liferay.frontend.taglib.clay (Maven): affected all versions; fixed in 15.2.1
- com.liferay:com.liferay.frontend.taglib.clay (Maven): affected all versions; fixed in 15.2.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-43774/ (Markdown: https://insights.sbomify.com/CVE-2025-43774/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-43774
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-43774
- OSV: https://osv.dev/vulnerability/CVE-2025-43774

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-43774/
Summaries are generated and may contain mistakes; the official description above is the record.