Skip to main content
VulnerabilityPublished

CVE-2026-14816: The GDPR Framework By Data443 (WordPress plugin) · Improper Access Control

Affects The GDPR Framework By Data443 (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.4.0 when convenient.

Data as of 2 Nov 2026, 22:58 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.4.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Upgrade The GDPR Framework By Data443 (WordPress plugin) to 2.4.0.

Affected software

ProductAffectedFixed in
The GDPR Framework By Data443Affected
  • <2.4.0
Fixed in
  • 2.4.0

AI-suggested

If you cannot patch yet, administrators should monitor for unusual activity related to privacy requests and consider restricting access or applying custom access controls if possible. Avoid relying on the plugin for critical privacy consent enforcement until patched.

Description

The GDPR Framework By Data443 WordPress plugin versions prior to 2.4.0 contains an improper access control vulnerability. This flaw allows unauthenticated attackers to forge cookie-consent records for arbitrary email addresses and to flood the site's privacy-request queue with arbitrary entries. The vulnerability arises from insufficient verification of authorization or the identity of the data subject when recording consent and privacy requests.

References

Community reviews

Loading reviews…