Skip to content
Web

CVE-2026-66656

HIGH
High
EPSS 0.34%Aug 13, 2026

Unauthenticated Local File Inclusion in Foton Core <=1.1.1 allowing arbitrary local file read

common questions

Is CVE-2026-66656 being exploited?

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

How severe is CVE-2026-66656?

CVE-2026-66656 is rated High. 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-66656?

Not known from our data. No patch reference has been recorded for CVE-2026-66656, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-66656 affect?

CVE-2026-66656 affects Foton Core <= 1.1.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-66656?

Apply vendor patch when available; restrict access, enable WAF and monitor for LFI indicators

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

executive summary
technical analysis
affected
Foton Core <= 1.1.1
impact

Unauthenticated LFI enables arbitrary local file read, exposing credentials, configs, source code; can be chained (log poisoning) for RCE.

action required

Immediate action required

affected versions
Mikado-Themes Foton Core
  • affected<= 1.1.1

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