CVE-2020-36875
Unauthenticated PHP code execution in AccessAlly WordPress plugin via login_error parameter.
Is CVE-2020-36875 being exploited?
Not confirmed. CVE-2020-36875 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.77% probability of exploitation in the next 30 days.
How severe is CVE-2020-36875?
CVE-2020-36875 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-2020-36875?
Yes. A fix has been recorded for CVE-2020-36875. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2020-36875 affect?
CVE-2020-36875 affects WordPress + AccessAlly plugin (<3.3.2). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2020-36875?
Upgrade to 3.3.2 or later
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
RCE via unauthenticated PHP execution in plugin; attacker can run PHP on the server, taking full site control.
Immediate action required
- affected< 3.3.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.