VulnerabilityPublished 2 Aug 2026Updated 3 Aug 2026

CVE-2026-13389: webtoffee-cookie-consent (WordPress plugin) · Missing Authorization

Affects webtoffee-cookie-consent (WordPress plugin)Source CVE Database V5

Compare

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

Data as of 1 Nov 2026, 08:20 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.5.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 31 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-xw6w-vrqp-fhq4

What to do

Upgrade webtoffee-cookie-consent (WordPress plugin) to 3.5.3.

Affected software

Product	Affected	Fixed in
webtoffee-cookie-consent	Affected <3.5.3	Fixed in 3.5.3

AI-suggested

If you cannot patch yet, restricting access to the REST API endpoints or disabling the plugin if feasible may reduce exposure.

Description

The webtoffee-cookie-consent WordPress plugin before version 3.5.3 contains missing authorization checks on multiple REST API routes. This flaw allows unauthenticated attackers to export and delete visitor consent records, create posts, and modify the plugin's licensing state. The vulnerability is tracked as CVE-2026-13389 and has a medium severity rating with a CVSS score of 6.5.

Impact

An attacker without authentication can exploit this vulnerability to access and delete visitor consent records, create arbitrary posts on the WordPress site, and modify the licensing state of the plugin. This can result in data loss, unauthorized content creation, and potential license misuse. The CVSS 3.1 base score is 6.5 (medium), reflecting the network attack vector, low attack complexity, no privileges required, no user interaction, and limited confidentiality and integrity impact without availability impact.

Summary

CVE-2026-13389 is a missing authorization vulnerability (CWE-862) in the webtoffee-cookie-consent WordPress plugin versions prior to 3.5.3. The plugin fails to enforce authorization on several REST API endpoints, enabling unauthenticated attackers to perform sensitive actions such as exporting and deleting stored visitor consent data, creating WordPress posts, and altering the plugin's licensing state. This lack of access control can lead to unauthorized data manipulation and potential disruption of site functionality.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/a591c79d-5db7-4716-8b6c-004b1195edf7/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Aug 2026, 15:06 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats