---
id: "CVE-2026-111908"
kind: "vulnerability"
aliases: ["CVE-2026-111908"]
title: "phpMyFAQ: edit permission lets users rewrite FAQs they cannot view"
severity: "high"
cvss: 8.7
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "php", "phpmyfaq", "self-hosted"]
not_affected_if: ["no-edit_faq-users", "version-4.1.9-or-later"]
published_at: "2026-10-17T19:16:33+00:00"
first_seen_at: "2026-10-23T21:57:14+00:00"
updated_at: "2026-10-23T22:37:35+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-111908", "first_seen_at": "2026-10-23T21:57:14+00:00"}]
---

# phpMyFAQ: edit permission lets users rewrite FAQs they cannot view

phpMyFAQ versions 4.0.0 before 4.1.9 and 4.2.0-alpha before 4.2.0-beta check only the global edit permission on the FAQ update API, not access to the specific FAQ. A logged-in user with edit rights can change restricted FAQs, bypass moderation and alter publication state.

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

## Fix

Upgrade phpMyFAQ to 4.1.9 or later, or to 4.2.0-beta or later if on the 4.2 line.

## Timeline

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

## From the sources

phpMyFAQ 4.0.0 before 4.1.9 and 4.2.0-alpha before 4.2.0-beta contains a broken object-level authorization vulnerability in the PUT /api/v3.1/faq/update endpoint, which checks only the global edit_faq permission and does not verify access to the target FAQ. Authenticated users with edit_faq permission can supply the ID of a restricted FAQ they cannot view to modify its content, bypass moderation, and change its publication state.

---

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