CVE-2026-35672
Unauthenticated API access in phpMyFAQ allows creating/modifying FAQ via v4.0 endpoints.
Is CVE-2026-35672 being exploited?
Not confirmed. CVE-2026-35672 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.38% probability of exploitation in the next 30 days.
How severe is CVE-2026-35672?
CVE-2026-35672 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-35672?
Yes. A fix has been recorded for CVE-2026-35672. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-35672 affect?
CVE-2026-35672 affects phpMyFAQ < 4.1.3. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-35672?
Upgrade to 4.1.3+; validate/clean injected data
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attackers bypass auth using empty x-pmf-token, enabling arbitrary FAQ/content modification via POST /api/v4.0/{faq/create,category,question}.
Patch when possible
- affected< 4.1.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.