CVE-2017-20246
Unauthenticated SQL injection in KittyCatfish WP plugin 2.2 exposes DB data via unescaped GET parameter.
Is CVE-2017-20246 being exploited?
Not confirmed. CVE-2017-20246 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.27% probability of exploitation in the next 30 days.
How severe is CVE-2017-20246?
CVE-2017-20246 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-2017-20246?
Not known from our data. No patch reference has been recorded for CVE-2017-20246, 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-2017-20246 affect?
CVE-2017-20246 affects KittyCatfish WordPress plugin 2.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2017-20246?
Update/patch plugin or remove
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Data disclosure: attacker can read database contents via boolean/time-based blind SQLi on kc_ad parameter.
Patch when possible
- affected2.2
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.