CVE-2026-130383

phpMyFAQ before 4.1.12 and 4.2.0-alpha.2 before 4.2.0-RC.2 Search Index Manipulation via solutionId

Published Nov 17, 2026 CVSS 4.0 · 5.1 Medium EPSS n/a KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

An authorization bypass flaw (CWE-639) allows authenticated editors to supply an arbitrary solutionId to the /admin/api/faq/update endpoint, enabling them to manipulate search index documents in Elasticsearch or OpenSearch deployments. This can remove published FAQs from search results, overwrite other FAQs’ search entries, or plant entries that remain searchable after the original FAQ is unpublished, thereby compromising the integrity of search results and potentially exposing or hiding content that should not be available. The vulnerability requires editor‑level authentication; it does not grant remote code execution but allows an attacker to disrupt the website’s informational content and propagate misinformation.

Affected Systems

phpMyFAQ versions earlier than 4.1.12 and 4.2.0-alpha.2 earlier than 4.2.0-RC.2, provided by thorsten: phpMyFAQ, are affected by this search‑index manipulation flaw.

Risk and Exploitability

The flaw is exploitable by any authenticated editor, which is a common role in an installation. The attacker can target Elasticsearch or OpenSearch back‑ends; the potential for misuse is significant in environments where users rely on search for critical information. While the impact is not catastrophic in terms of system compromise, it undermines content integrity and can facilitate malicious content persistence. Because the score is moderate and no exploitation evidence exists in KEV, the urgency is still high for installations that expose the affected API endpoint.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade phpMyFAQ to version 4.1.12 or 4.2.0‑RC.2 or later.
  • If an upgrade is delayed, restrict editor permissions so the solutionId parameter can no longer be changed via the /admin/api/faq/update endpoint or disable that endpoint entirely for Elasticsearch/OpenSearch back‑ends.
  • Configure network or application firewall rules to block external access to the /admin/api/faq/update endpoint until the patch is applied.

Generated by OpenCVE AI on November 17, 2026 at 03:08 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description 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.
Title phpMyFAQ before 4.1.12 and 4.2.0-alpha.2 before 4.2.0-RC.2 Search Index Manipulation via solutionId
First Time appeared Phpmyfaq
Phpmyfaq phpmyfaq
Weaknesses CWE-639
CPEs cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:*
Vendors & Products Phpmyfaq
Phpmyfaq phpmyfaq
References
Metrics cvssV3_1

{'score': 3.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L'}

cvssV4_0

{'score': 5.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 17, 2026, 1:40 AM
Reserved
Nov 17, 2026, 1:09 AM
Status
Deferred
Published
Nov 17, 2026, 2:17 AM
Modified
Nov 17, 2026, 2:17 AM