# Liferay Portal Vulnerable to XSS in Profile Search Functionality

Advisory record · `GHSA-hq29-vqg6-pjpw`

- **Identifiers:** `GHSA-hq29-vqg6-pjpw` · `CVE-2016-3670`
- **State:** Confirmed
- **Severity:** CVSS 6.1 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-79](https://cwe.mitre.org/data/definitions/79.html)
- **Tags:** [Cross-site scripting (XSS)](https://agentprime.io/advisories/tag/xss.md)
- **Published:** 17 May 2022
- **Updated:** 8 Aug 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 May 2022, 03:53 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `com.liferay:com.liferay.portal.search.web` (Maven): affected `<1.0.3`; fixed in `1.0.3`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Liferay Portal Search Web (com.liferay.portal.search.web) versions before 1.0.3 are vulnerable to cross-site scripting in the Profile Search functionality, where the FirstName field is not properly sanitized. A remote attacker can inject arbitrary web script or HTML, which can execute in other users' browsers. Upgrade to version 1.0.3 or later.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.1 Medium, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.025, the 84th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:10 UTC: First seen by agentprime
- 31 Oct 2026, 15:10 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-hq29-vqg6-pjpw)

## Sources

- [GitHub Advisory Database: GHSA-hq29-vqg6-pjpw](https://github.com/advisories/GHSA-hq29-vqg6-pjpw)
- [OSV: GHSA-hq29-vqg6-pjpw](https://osv.dev/vulnerability/GHSA-hq29-vqg6-pjpw)
- <https://nvd.nist.gov/vuln/detail/CVE-2016-3670>
- <https://github.com/liferay/liferay-portal/commit/b7ce087039f3b753f36f558df5faefac4ad4b160>
- <https://github.com/liferay/liferay-portal>
- <https://issues.liferay.com/browse/LPS-62387>
- <https://labs.integrity.pt/advisories/cve-2016-3670>
- <https://www.exploit-db.com/exploits/39880>
- <http://packetstormsecurity.com/files/137279/Liferay-CE-Stored-Cross-Site-Scripting.html>
- <http://seclists.org/fulldisclosure/2016/Jun/5>
- <http://www.securitytracker.com/id/1036083>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-hq29-vqg6-pjpw>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-hq29-vqg6-pjpw/>. Everything for agents: <https://agentprime.io/llms.txt>.
