WP Data Access Plugin up to 5.5.76 on WordPress REST endpoint authorization

Summaryinfo

A vulnerability was found in WP Data Access Plugin up to 5.5.76. It has been rated as problematic. The affected element is an unknown function of the component REST endpoint. This manipulation causes authorization. This vulnerability appears as CVE-2026-106098. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as problematic was found in WP Data Access Plugin up to 5.5.76. Affected by this vulnerability is an unknown function of the component REST endpoint. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. As an impact it is known to affect integrity. The summary by CVE is:

The WP Data Access WordPress plugin before 5.5.77 does not correctly check authorization on one of its application REST endpoints, verifying only read permission before performing a write, which allows unauthenticated attackers to modify data in an application exposed for anonymous read access even when update actions have been disabled by the administrator.

The advisory is shared at wpscan.com. This vulnerability is known as CVE-2026-106098 since 10/06/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.

Upgrading to version 5.5.77 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• WordPress Plugin

Name

• WP Data Access Plugin

Version

• 5.5.0
• 5.5.1
• 5.5.2
• 5.5.3
• 5.5.4
• 5.5.5
• 5.5.6
• 5.5.7
• 5.5.8
• 5.5.9
• 5.5.10
• 5.5.11
• 5.5.12
• 5.5.13
• 5.5.14
• 5.5.15
• 5.5.16
• 5.5.17
• 5.5.18
• 5.5.19
• 5.5.20
• 5.5.21
• 5.5.22
• 5.5.23
• 5.5.24
• 5.5.25
• 5.5.26
• 5.5.27
• 5.5.28
• 5.5.29
• 5.5.30
• 5.5.31
• 5.5.32
• 5.5.33
• 5.5.34
• 5.5.35
• 5.5.36
• 5.5.37
• 5.5.38
• 5.5.39
• 5.5.40
• 5.5.41
• 5.5.42
• 5.5.43
• 5.5.44
• 5.5.45
• 5.5.46
• 5.5.47
• 5.5.48
• 5.5.49
• 5.5.50
• 5.5.51
• 5.5.52
• 5.5.53
• 5.5.54
• 5.5.55
• 5.5.56
• 5.5.57
• 5.5.58
• 5.5.59
• 5.5.60
• 5.5.61
• 5.5.62
• 5.5.63
• 5.5.64
• 5.5.65
• 5.5.66
• 5.5.67
• 5.5.68
• 5.5.69
• 5.5.70
• 5.5.71
• 5.5.72
• 5.5.73
• 5.5.74
• 5.5.75
• 5.5.76

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion