CVE-2026-130383: thorsten phpMyFAQ · Insecure Direct Object Reference
Affects thorsten phpMyFAQSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium : upgrade to 4.2.0-RC.2 or 4.1.12 when convenient.
Data as of 17 Nov 2026, 02:04 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 5.1 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 3.8 |
- Patch
- Available – fixed in 4.2.0-RC.2, 4.1.12
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade thorsten phpMyFAQ to 4.2.0-RC.2 or 4.1.12.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| thorstenphpMyFAQ | Affected
| Fixed in
|
| thorstenphpMyFAQ | Affected
| Fixed in
|
PackagistphpMyFAQpkg:composer/phpMyFAQOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade phpMyFAQ to version 4.1.12 or later, or to 4.2.0-RC.2 or later, where this authorization bypass vulnerability is fixed. No other mitigations are indicated. Applying these updates will prevent unauthorized manipulation of search index documents via the /admin/api/faq/update endpoint.
Description
phpMyFAQ versions before 4.1.12 and between 4.2.0-alpha.2 and before 4.2.0-RC.2 contain an authorization bypass vulnerability. Authenticated editors can manipulate search index documents by supplying arbitrary solutionId values to the /admin/api/faq/update endpoint. This allows category-restricted editors on Elasticsearch or OpenSearch deployments to remove published FAQs from search results, overwrite other FAQs' search documents, or create entries that remain searchable after unpublishing.
References
- github.com/thorsten/phpMyFAQ/commit/2a62324de93736d193058d2b4b95de4f57922b1b (opens in a new tab)
- github.com/thorsten/phpMyFAQ/commit/44fbf492437ea87dca01acb904616656502ff251 (opens in a new tab)
- github.com/thorsten/phpMyFAQ/blob/4.2.0-RC.1/phpmyfaq/src/phpMyFAQ/Controller/Administration/Api/FaqController.php (opens in a new tab)
- github.com/thorsten/phpMyFAQ/releases/tag/4.1.12 (opens in a new tab)
- github.com/thorsten/phpMyFAQ/releases/tag/4.2.0-RC.2 (opens in a new tab)
- 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 (opens in a new tab)