CVE-2026-62068
Unauthenticated Local File Inclusion in Teoro WordPress theme ≤1.1
Is CVE-2026-62068 being exploited?
Not confirmed. CVE-2026-62068 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.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-62068?
CVE-2026-62068 is rated High with a CVSS score of 8.1. 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-62068?
Not known from our data. No patch reference has been recorded for CVE-2026-62068, 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-62068 affect?
CVE-2026-62068 affects Teoro WordPress theme <= 1.1, WordPress sites using Teoro theme. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-62068?
Disable/remove Teoro theme; restrict file access; apply vendor patch when available.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated LFI allows reading local files (e.g., wp-config.php), exposing credentials and potentially enabling RCE via log/file poisoning.
Immediate action required
- affected<= 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.