---
id: "CVE-2026-130383"
page: "https://infrastack.ai/live/CVE-2026-130383"
kind: "vulnerability"
aliases: ["CVE-2026-130383"]
title: "phpMyFAQ: editors can tamper with other FAQs' search index entries"
severity: "medium"
cvss: 5.1
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["elasticsearch", "opensearch", "package", "php", "phpmyfaq"]
not_affected_if: ["auth-required", "default-config"]
published_at: "2026-11-17T02:17:22+00:00"
first_seen_at: "2026-11-17T02:40:33+00:00"
updated_at: "2026-11-17T02:42:45+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-130383", "first_seen_at": "2026-11-17T02:40:33+00:00"}]
exploit_sources: []
---

# phpMyFAQ: editors can tamper with other FAQs' search index entries

Link for people: https://infrastack.ai/live/CVE-2026-130383 (this .md is for agents)

phpMyFAQ before 4.1.12 and 4.2.0-alpha.2 before 4.2.0-RC.2 lets an authenticated editor pass an arbitrary solutionId to the /admin/api/faq/update endpoint. On Elasticsearch or OpenSearch setups, a category-restricted editor can remove published FAQs from search, overwrite other FAQs' search documents, or leave entries searchable after unpublishing.

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

## How to check

- Check the installed phpMyFAQ version in the admin panel or `composer show phpmyfaq/phpmyfaq` if installed via Composer.
- Check whether the search backend is Elasticsearch or OpenSearch in the phpMyFAQ configuration.

## Fix

- phpMyFAQ `4.1.12` for the 4.1 line
- phpMyFAQ `4.2.0-RC.2` for the 4.2 alpha line

## Timeline

- 2026-11-17T02:40:33+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-130383

## Documents

- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/phpmyfaq-before-4.1.12-and-4.2.0-alpha.2-before-4.2.0-rc.2-search-index-manipulation-via-solutionid
- [fix] Patch: github.com https://github.com/thorsten/phpMyFAQ/commit/2a62324de93736d193058d2b4b95de4f57922b1b
- [fix] Patch: github.com https://github.com/thorsten/phpMyFAQ/commit/44fbf492437ea87dca01acb904616656502ff251
- [fix] Release notes: github.com https://github.com/thorsten/phpMyFAQ/releases/tag/4.1.12
- [fix] Release notes: github.com https://github.com/thorsten/phpMyFAQ/releases/tag/4.2.0-RC.2

## From the sources

phpMyFAQ before 4.1.12 and 4.2.0-alpha.2 before 4.2.0-RC.2 contains an authorization bypass vulnerability that allows authenticated editors to manipulate search index documents by supplying an arbitrary solutionId to the /admin/api/faq/update endpoint. On Elasticsearch or OpenSearch deployments, category-restricted editors can remove published FAQs from search, overwrite other FAQs' search documents, or plant entries that remain searchable after unpublishing.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
