CVE-2017-20251
Unauthenticated code injection in WordPress Insert PHP plugin <=3.3.1 via REST API.
Is CVE-2017-20251 being exploited?
Not confirmed. CVE-2017-20251 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.56% probability of exploitation in the next 30 days.
How severe is CVE-2017-20251?
CVE-2017-20251 is rated Critical with a CVSS score of 9.3. 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-2017-20251?
Yes. A fix has been recorded for CVE-2017-20251. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2017-20251 affect?
CVE-2017-20251 affects WordPress Insert PHP plugin <=3.3.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2017-20251?
Upgrade to 3.3.1+ or remove plugin
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote PHP code execution via crafted insert_php shortcode in wp-json/wp/v2/posts; full server compromise possible.
Immediate action required
- affected< 3.3.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.