> ## Content Index
> Fetch the complete content index at: https://ping2prompt.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# phpMyFAQ 4.1.12 fixes editor tampering with Elasticsearch and OpenSearch data
- URL: https://ping2prompt.com/phpmyfaq-4-1-12-fixes-editor-search-index-tampering/
- Published: 2026-11-17T02:40:22.000Z
- Updated: 2026-11-18T17:21:28.000Z
- Description: phpMyFAQ has an authorization bypass, CVE-2026-130383, letting logged-in editors alter Elasticsearch or OpenSearch documents, such as removing published FAQs from search. Exploitation status is unknown. Update to 4.1.12, or 4.2.0-RC.2 on pre-releases.
- Author: Ping2Prompt Newsroom
- Tags: Vulnerabilities, Medium, #short-ping

## Editors can tamper with phpMyFAQ search results

phpMyFAQ has an authorization bypass, tracked as CVE-2026-130383, that lets an authenticated editor manipulate documents in the search index. It scores 5.1 under CVSS 4.0, which is medium severity. The vector rates the impact on integrity and availability as low and confidentiality as none for the vulnerable system.

Editors limited to certain categories can remove published FAQs from search or overwrite the search documents of other FAQs. They can also plant entries that stay searchable after the FAQ is unpublished.

## The FAQ update endpoint accepts any solutionId

The flaw sits in the `/admin/api/faq/update` endpoint of the admin FaqController. An editor supplies an arbitrary `solutionId` to that endpoint, and the request reaches search documents the editor should not control. The attack works over the network but requires high privileges, meaning a logged-in editor account.

## phpMyFAQ before 4.1.12 on Elasticsearch or OpenSearch

Affected versions are phpMyFAQ before 4.1.12, and 4.2.0-alpha.2 up to but not including 4.2.0-RC.2\. The issue applies to deployments that use Elasticsearch or OpenSearch as the search backend. Check which release you run in the admin area, and check which search backend you configured. The sources do not say whether the flaw is being exploited. Unknown is not safe, so treat the update as due if you give editor accounts to people you do not fully trust.

## Update to phpMyFAQ 4.1.12 or 4.2.0-RC.2

Upgrade to 4.1.12 on the stable branch, or 4.2.0-RC.2 if you run the 4.2 pre-releases. These versions come from the release tags in the CVE references, not from release notes. The references also list two fix commits, `2a62324de93736d193058d2b4b95de4f57922b1b` and `44fbf492437ea87dca01acb904616656502ff251`. No workaround is given in the sources, so limiting who holds editor accounts is the only stopgap they point toward, and they do not confirm it.

## What the CVE record leaves out

The NVD record is marked Deferred, and it gives no disclosure or patch dates.

| Product                   | Affected                        | Fixed      |
| ------------------------- | ------------------------------- | ---------- |
| phpMyFAQ 4.1 branch       | before 4.1.12                   | 4.1.12     |
| phpMyFAQ 4.2 pre-releases | 4.2.0-alpha.2 before 4.2.0-RC.2 | 4.2.0-RC.2 |

## Sources

- [nvd.nist.gov/vuln/detail/CVE-2026-130383](https://nvd.nist.gov/vuln/detail/CVE-2026-130383?ref=ping2prompt.com)

---

This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our [editorial methodology](https://ping2prompt.com/about-how-we-work/) and the [corrections log](https://ping2prompt.com/corrections/). Spotted an error? Email [editor@ping2prompt.com](mailto:editor@ping2prompt.com).