CVE-2026-130383
Deferred Deferred - Pending Action

Authorization Bypass in phpMyFAQ via Search Index Manipulation

Vulnerability report for CVE-2026-130383, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-17

Last updated on: 2026-11-17

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-17
Last Modified
2026-11-17
Generated
2026-11-17
AI Q&A
2026-11-17
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
phpmyfaq phpmyfaq to 4.1.12 (exc)
phpmyfaq phpmyfaq From 4.2.0-alpha.2 (inc) to 4.2.0-RC.2 (exc)
thorsten phpmyfaq to 4.2.0-alpha.2 (exc)
thorsten phpmyfaq 4.2.0-rc.1

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is an authorization bypass in phpMyFAQ versions before 4.1.12 and 4.2.0-alpha.2 before 4.2.0-RC.2. It allows authenticated editors to manipulate search index documents by submitting a custom solutionId to the /admin/api/faq/update endpoint. The issue specifically affects deployments using Elasticsearch or OpenSearch, enabling category-restricted editors to delete published FAQs from search results, overwrite other FAQs' search documents, or insert entries that remain searchable after unpublishing.

Detection Guidance

Check phpMyFAQ logs for suspicious /admin/api/faq/update endpoint requests with custom solutionId parameters. Inspect Elasticsearch/OpenSearch indices for unexpected document deletions, overwrites, or unauthorized entries. Review API access logs for editors making bulk updates outside their category scope.

Impact Analysis

If exploited, this vulnerability could allow unauthorized users to remove FAQs from search results, modify or overwrite existing FAQ search documents, or plant misleading entries that persist even after unpublishing. This could lead to misinformation, data integrity issues, or unauthorized access to sensitive information depending on the FAQ content.

Compliance Impact

This vulnerability could impact compliance with GDPR and HIPAA by enabling unauthorized modifications to search index documents. Attackers could overwrite or delete FAQ entries, potentially altering or removing sensitive information stored in phpMyFAQ deployments. This could lead to unauthorized data exposure, integrity violations, or failure to maintain accurate records, which are critical requirements under GDPR and HIPAA.

Mitigation Strategies

Upgrade phpMyFAQ to version 4.1.12 or 4.2.0-RC.2 or later. Restrict editor permissions to minimum required levels. Monitor search index changes and revert unauthorized modifications. Review all FAQ entries for integrity after update.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-130383. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...