CVE-2020-36718 json
GDPR CCPA Compliance Support <= 2.3 - PHP Object Injection
published 2023-06-07 3 y ago modified 2026-06-17 4 mo ago also EUVD-2020-24160
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
The GDPR CCPA Compliance Support plugin for WordPress is vulnerable to PHP Object Injection in versions up to, and including, 2.3 via deserialization of untrusted input "njt_gdpr_allow_permissions" value. This allows unauthenticated attackers to inject a PHP Object.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 22 mo ago
Exploit prediction
1.72% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- blog.nintechnet.com https://blog.nintechnet.com/gdpr-ccpa-compliance-support-plugin-fixed-insecure-deserialization-vulnerability/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- ninjateam GDPR CCPA Compliance & Cookie Consent Banner
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
- Technology feeds
References
-
plugins.trac.wordpress.org
/changeset/2408938
patch
-
plugins.trac.wordpress.org
/changeset/2411356/ninja-gdpr-compliance
patch
-
blog.nintechnet.com
/gdpr-ccpa-compliance-support-plugin-fixed-insecure-deserialization-vulnerability/
exploit
-
wordfence.com
/threat-intel/vulnerabilities/id/a2871261-3231-4a52-9a38-bb3caf461e7d?source=cve
third-party-advisory
-
wordpress.org
/plugins/ninja-gdpr-compliance/#developers
product
-
wpscan.com
/vulnerability/92f1d6fb-c665-419e-a13b-688b1df6c395
third-party-advisory
Sources
- CVE List CVE-2020-36718
- NVD CVE-2020-36718
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.