Skip to content
Web

CVE-2026-62086

9.8
Critical
EPSS 0.39%Oct 11, 2026

Unauthenticated PHP Object Injection in Juno WordPress theme <=2.25

common questions

Is CVE-2026-62086 being exploited?

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

How severe is CVE-2026-62086?

CVE-2026-62086 is rated Critical with a CVSS score of 9.8. 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-62086?

Not known from our data. No patch reference has been recorded for CVE-2026-62086, 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-62086 affect?

CVE-2026-62086 affects Juno WordPress theme <= 2.25, WordPress sites using the Juno theme. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-62086?

Disable/remove Juno theme, isolate affected sites, enable WAF rules, apply vendor patch when released

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

executive summary
technical analysis
affected
Juno WordPress theme <= 2.25WordPress sites using the Juno theme
impact

Unauthenticated PHP object injection leads to arbitrary object deserialization enabling remote code execution, site takeover, data access or persistent backdoors.

action required

Immediate action required

affected versions
ThemeREX Juno
  • affected<= 2.25

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