# phpMyFAQ has Stored XSS in user list via admin-managed display_name

Advisory record · `GHSA-jv8r-hv7q-p6vc`

- **Identifiers:** `GHSA-jv8r-hv7q-p6vc` · `CVE-2025-68951` · `PKSA-hj4y-1t5r-b8zy`
- **State:** Confirmed
- **Severity:** CVSS 5.4 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:** 29 Dec 2025
- **Updated:** 3 Feb 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 29 Dec 2025, 22:12 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `thorsten/phpmyfaq` (Packagist): affected `>=4.0.14, <4.0.16`; fixed in `4.0.16`

## Machine-written summary

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

> Stored XSS in thorsten/phpmyfaq versions >=4.0.14 and <4.0.16 lets a registered user plant script in the display name field, which runs in an administrator's browser when they view the admin user list. The attacker needs only an account on a site with registration enabled, and can then act in the admin context, such as hijacking the session or performing privileged actions. Upgrade to 4.0.16.

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

- 5.4 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0028, the 21st percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:26 UTC: First seen by agentprime
- 31 Oct 2026, 14:26 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jv8r-hv7q-p6vc)

## Sources

- [GitHub Advisory Database: GHSA-jv8r-hv7q-p6vc](https://github.com/advisories/GHSA-jv8r-hv7q-p6vc)
- [OSV: GHSA-jv8r-hv7q-p6vc](https://osv.dev/vulnerability/GHSA-jv8r-hv7q-p6vc)
- <https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-jv8r-hv7q-p6vc>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-68951>
- <https://github.com/thorsten/phpMyFAQ/commit/61829e83411f7b28bc6fd1052bfde54c32c6c370>
- <https://github.com/thorsten/phpMyFAQ/commit/8211d1d25951b4c272443cfc3ef9c09b1363fd87>
- <https://github.com/thorsten/phpMyFAQ>

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-jv8r-hv7q-p6vc>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jv8r-hv7q-p6vc/>. Everything for agents: <https://agentprime.io/llms.txt>.
