How severe is CVE-2020-36875?

CVE-2020-36875 has a CVSS 4.0 base score of 9.3, rated critical severity.

Is CVE-2020-36875 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2020-36875?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2020-36875 have an EU (EUVD) identifier?

Yes. CVE-2020-36875 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-1714.

When was CVE-2020-36875 published?

CVE-2020-36875 was published on 2026-01-09 and last updated on 2026-06-17.

CVE-2020-36875

CVE-2020-36875 is a critical-severity vulnerability with a CVSS 4.0 base score of 9.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-94.

Key facts

Severity: Critical (CVSS 4.0 base score 9.3)
EPSS exploit prediction: 1% (50th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-1714
Weakness: CWE-94
Published: 2026-01-09
Last modified: 2026-06-17

Description

AccessAlly WordPress plugin versions prior to 3.3.2 contain an unauthenticated arbitrary PHP code execution vulnerability in the Login Widget. The plugin processes the login_error parameter as PHP code, allowing an attacker to supply and execute arbitrary PHP in the context of the WordPress web server process, resulting in remote code execution.

Frequently asked questions

What is CVE-2020-36875?: AccessAlly WordPress plugin versions prior to 3.3.2 contain an unauthenticated arbitrary PHP code execution vulnerability in the Login Widget. The plugin processes the login_error parameter as PHP code, allowing an attacker to supply and execute arbitrary PHP in the context of the WordPress web server process, resulting in remote code execution.
How severe is CVE-2020-36875?: CVE-2020-36875 has a CVSS 4.0 base score of 9.3, rated critical severity.
Is CVE-2020-36875 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2020-36875?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2020-36875 have an EU (EUVD) identifier?: Yes. CVE-2020-36875 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-1714.
When was CVE-2020-36875 published?: CVE-2020-36875 was published on 2026-01-09 and last updated on 2026-06-17.

References

Other CWE-94 (Code Injection) vulnerabilities

CVE-2026-57624 — Critical (CVSS 10.0): Unauthenticated Remote Code Execution (RCE) in Blocksy Companion Pro <= 2.1.46 versions.
CVE-2026-10134 — Critical (CVSS 10.0): IBM Langflow OSS 1.0.0 through 1.9.3 allows an attacker to read every secret available to the Langflow process, read…
CVE-2026-53576 — Critical (CVSS 10.0): Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, the authentication filter…
CVE-2026-10561 — Critical (CVSS 10.0): IBM Langflow OSS 1.0.0 through 1.9.3 has an vulnerability due to an improper isolation of Python execution combined…
CVE-2026-25470 — Critical (CVSS 10.0): Improper Control of Generation of Code ('Code Injection') vulnerability in ACPT ACPT (Pro) - Custom Post Types Plugin…
CVE-2026-48836 — Critical (CVSS 10.0): Unauthenticated Remote Code Execution (RCE) in Easy Invoice <= 2.1.19 versions.

Browse all CWE-94 (Code Injection) vulnerabilities →