CVE-2020-36730: The CMP for WordPress is vulnerable to authorization bypass due to a missing capability check on the cmp_get_p

Q: How do I fix CVE-2020-36730?

cmp: upgrade to newer than 3.8.1. Exact commands for each OS are on this page.

Q: Is CVE-2020-36730 being exploited?

CVE-2020-36730 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-36730 affect?

CVE-2020-36730 affects cmp. Severity is high (CVSS 8.3). The CMP for WordPress is vulnerable to authorization bypass due to a missing capability check on the cmp_get_post_detail(), niteo_export_csv(), and cmp_disable_comingsoon_ajax() functions in versions up to, and including, 3.8.1. This makes

Q: How urgent is CVE-2020-36730?

Priority 60/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 8.3REMOTEUPGRADE

CVE-2020-36730 is a high-severity flaw (CVSS 8.3) affecting cmp. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The CMP for WordPress is vulnerable to authorization bypass due to a missing capability check on the cmp_get_post_detail(), niteo_export_csv(), and cmp_disable_comingsoon_ajax() functions in versions up to, and including, 3.8.1. This makes it possible for unauthenticated attackers to read posts, export subscriber lists, and/or deactivate the plugin.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.3 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.3% (top 17%)
CISA exploited list	No
Weakness	CWE-862
Published	2023-06-07
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: niteothemes

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-06-07 02:15 UTCPublished CVE record published
2026-06-17 03:16 UTCUpdated Record last modified

niteothemes cmp UPGRADE

Affected: <= 3.8.1

Fixed in: newer than 3.8.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy cmp || rpm -q cmp || cmp --version

2. UPGRADE to newer than 3.8.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade cmp

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade cmp

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-36730?

cmp: upgrade to newer than 3.8.1. Exact commands for each OS are on this page.

Is CVE-2020-36730 being exploited?

CVE-2020-36730 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-36730 affect?

CVE-2020-36730 affects cmp. Severity is high (CVSS 8.3). The CMP for WordPress is vulnerable to authorization bypass due to a missing capability check on the cmp_get_post_detail(), niteo_export_csv(), and cmp_disable_comingsoon_ajax() functions in versions up to, and including, 3.8.1. This makes

How urgent is CVE-2020-36730?

Priority 60/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2023-2159 MEDIUM 5.3 UPGRADE The CMP – Coming Soon & Maintenance plugin for WordPress is vulnerable to Maintenance Mode Bypass in versions

References

← Back to latest CVEs