Skip to content
Web

CVE-2026-66397

8.6
High
EPSS 0.33%Patch availableJul 28, 2026

Authenticated path traversal in phpMyFAQ <4.1.6 allows file deletion and admin takeover.

common questions

Is CVE-2026-66397 being exploited?

Not confirmed. CVE-2026-66397 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.33% probability of exploitation in the next 30 days.

How severe is CVE-2026-66397?

CVE-2026-66397 is rated High with a CVSS score of 8.6. 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-66397?

Yes. A fix has been recorded for CVE-2026-66397. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-66397 affect?

CVE-2026-66397 affects phpMyFAQ < 4.1.6, phpMyFAQ installations with image upload enabled, Web servers hosting phpMyFAQ. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-66397?

Upgrade to phpMyFAQ 4.1.6+, restrict public setup access, inspect/restore database.php, review logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
phpMyFAQ < 4.1.6phpMyFAQ installations with image upload enabledWeb servers hosting phpMyFAQ
impact

Authenticated attackers can delete arbitrary files (e.g., database.php), disable install gate and create new superadmin accounts via public setup wizard.

action required

Immediate action required

affected versions
thorsten phpMyFAQ
  • affected< 4.1.6
vendor says fixed in4.1.6

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free