---
id: "CVE-2026-111904"
kind: "vulnerability"
aliases: ["CVE-2026-111904"]
title: "phpMyFAQ: open-questions API leaks hidden questions and usernames to anonymous users"
severity: "medium"
cvss: 6.9
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "php", "phpmyfaq", "self-hosted"]
not_affected_if: ["default-config"]
published_at: "2026-10-17T19:16:32+00:00"
first_seen_at: "2026-10-23T21:57:14+00:00"
updated_at: "2026-10-25T03:41:06+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-111904", "first_seen_at": "2026-10-23T21:57:14+00:00"}]
---

# phpMyFAQ: open-questions API leaks hidden questions and usernames to anonymous users

phpMyFAQ 4.2.0-alpha before 4.2.0-beta has an inverted check in its open-questions controller, so the public API returns non-public moderation questions. An unauthenticated attacker can send GET requests to /api/v4.0/open-questions and read those questions along with the usernames attached to them.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed version in the phpMyFAQ admin panel or the release files; affected versions are `4.2.0-alpha` up to but not including `4.2.0-beta`.
- Request `/api/v4.0/open-questions` from outside the network without logging in and see whether non-public questions appear in the response.

## Fix

- Upgrade phpMyFAQ to `4.2.0-beta` or later.
- Until upgraded, restrict access to `/api/v4.0/open-questions` at the web server or proxy.

## Timeline

- 2026-10-23T21:57:14+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-111904

## From the sources

phpMyFAQ 4.2.0-alpha before 4.2.0-beta contains an information disclosure vulnerability that allows unauthenticated attackers to read hidden open questions due to an inverted api.onlyPublicQuestions check in OpenQuestionController. Attackers can send GET requests to the /api/v4.0/open-questions endpoint to retrieve non-public moderation or internal questions and their associated usernames.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_