CVE-2026-105436
Object-injection via deserialization in MainWP Child WordPress plugin allowing site compromise.
Is CVE-2026-105436 being exploited?
Not confirmed. CVE-2026-105436 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.25% probability of exploitation in the next 30 days.
How severe is CVE-2026-105436?
CVE-2026-105436 is rated High with a CVSS score of 8.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-105436?
Not known from our data. No patch reference has been recorded for CVE-2026-105436, 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-105436 affect?
CVE-2026-105436 affects MainWP Child WordPress plugin <= 6.2.1, WordPress sites using MainWP Child. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-105436?
Deactivate/remove plugin or restrict access; apply vendor patch when available.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted serialized payloads enable PHP object injection potentially leading to remote code execution, site takeover, or data compromise.
Immediate action required
- affected<= 6.2.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.