CVE-2020-36697: The WP GDPR plugin for WordPress is vulnerable to authorization bypass due to a missing capability check in ve

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

wp gdpr: upgrade to newer than 2.1.1. Exact commands for each OS are on this page.

Q: Is CVE-2020-36697 being exploited?

CVE-2020-36697 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-36697 affect?

CVE-2020-36697 affects wp gdpr. Severity is high (CVSS 7.3). The WP GDPR plugin for WordPress is vulnerable to authorization bypass due to a missing capability check in versions up to, and including, 2.1.1. This makes it possible for unauthenticated attackers to delete any comment and modify the plug

Q: How urgent is CVE-2020-36697?

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

This week

HIGH 7.3REMOTEUPGRADE

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

The WP GDPR plugin for WordPress is vulnerable to authorization bypass due to a missing capability check in versions up to, and including, 2.1.1. This makes it possible for unauthenticated attackers to delete any comment and modify the plugin’s settings.

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	7.3 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.9% (top 42%)
CISA exploited list	No
Weakness	CWE-862
Published	2023-06-07
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: appsaloon

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:15 UTCUpdated Record last modified

appsaloon wp gdpr UPGRADE

Affected: <= 2.1.1

Fixed in: newer than 2.1.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-gdpr || rpm -q wp-gdpr || wp-gdpr --version

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

sudo apt update && sudo apt install --only-upgrade wp-gdpr

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-gdpr

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-36697?

wp gdpr: upgrade to newer than 2.1.1. Exact commands for each OS are on this page.

Is CVE-2020-36697 being exploited?

CVE-2020-36697 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-36697 affect?

CVE-2020-36697 affects wp gdpr. Severity is high (CVSS 7.3). The WP GDPR plugin for WordPress is vulnerable to authorization bypass due to a missing capability check in versions up to, and including, 2.1.1. This makes it possible for unauthenticated attackers to delete any comment and modify the plug

How urgent is CVE-2020-36697?

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

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs