CVE-2026-130383
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network with an admin-level account. Limited direct impact.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 5.1 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-639 · Insecure direct object reference
- Record status
- Deferred
Attack profile CVSS 4.0 · 5.1
- Attack vector
- Network
- Complexity
- Low
- Attack requirements
- None
- Privileges needed
- High
- User interaction
- None
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
Raw 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-130383.md and follow it. Check whether this project is affected by CVE-2026-130383. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/thorsten/phpMyFAQ/commit/2a62324de93736d193058d2b4b95de4f57922b1b
- https://github.com/thorsten/phpMyFAQ/commit/44fbf492437ea87dca01acb904616656502ff251
- https://github.com/thorsten/phpMyFAQ/releases/tag/4.1.12
- https://github.com/thorsten/phpMyFAQ/releases/tag/4.2.0-RC.2
References
- https://github.com/thorsten/phpMyFAQ/blob/4.2.0-RC.1/phpmyfaq/src/phpMyFAQ/Controller/Administration/Api/FaqController.php#L405
- https://github.com/thorsten/phpMyFAQ/commit/2a62324de93736d193058d2b4b95de4f57922b1b
- https://github.com/thorsten/phpMyFAQ/commit/44fbf492437ea87dca01acb904616656502ff251
- https://github.com/thorsten/phpMyFAQ/releases/tag/4.1.12
- https://github.com/thorsten/phpMyFAQ/releases/tag/4.2.0-RC.2
- 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