WP GDPR Compliance <= 1.4.2 - Arbitrary Options Update and Action Calling
Strategic Overview
- Status
- Patched in 1.4.3
- Affected Plugin
- Cookie Information | Free GDPR Consent Solution
- Affected Version
< 1.4.3- CVSS
- 9.8Critical
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE-2018-19207
At a glance
CVE-2018-19207 is a critical-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Cookie Information WordPress plugin, affecting versions < 1.4.3. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.4.3; sites on affected versions should update now. Disclosed November 2018, reported by Adrian Mörchen.
Vulnerability Overview
The WP GDPR Compliance plugin for WordPress is vulnerability to arbitrary options updates and action calling in versions up to, and including 1.4.2 due to insufficient capability checking on the wpgdprc_process_action AJAX action. This missing it possible for unauthenticated attackers to trigger the AJAX action and make updates to the sites options that can be used to create administrative user accounts.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-94: Improper Control of Generation of Code ('Code Injection')
Reaching this weakness in Cookie Information < 1.4.3 takes a caller who can reach the endpoint. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.
The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For Cookie Information the fix is 1.4.3: builds < 1.4.3 are affected, anything from 1.4.3 onward is not.
Remediation
Update to version 1.4.3, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Cookie Information: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Cookie Information 1.4.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in Cookie Information | Free GDPR Consent Solution
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C