CVE-2026-3235

WP Data Access – No-Code App Builder with Tables, Forms, Charts & Maps <= 5.5.68 - Unauthenticated Insecure Direct Object Reference to Data Access

2026-08-25 00:00
type5afe

Strategic Overview

Status
Patched in 5.5.69
Affected Plugin
WP Data Access – App Builder for Tables, Forms, Dashboards, Charts & Maps
Affected Version
<= 5.5.68
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-3235
View all WP Data Access – App Builder for Tables, Forms, Dashboards, Charts & Maps vulnerabilities

At a glance

CVE-2026-3235 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WP Data Access WordPress plugin, affecting versions <= 5.5.68. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.5.69; sites on affected versions should update now. Disclosed August 2026, reported by type5afe.

Vulnerability Overview

The WP Data Access plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.5.68 via the 'check_app_access' function due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to access data from protected app containers by exploiting a mismatch between the authorization check (performed against app_id) and data retrieval (performed using cnt_id without verifying container ownership).

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.

CWE-639: Authorization Bypass Through User-Controlled Key

WP Data Access <= 5.5.68 carries this weakness at check_app_access, and reaching it takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For WP Data Access the fix is 5.5.69: builds <= 5.5.68 are affected, anything from 5.5.69 onward is not.

Remediation

Update to version 5.5.69, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WP Data Access 5.5.69 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-3235https://www.wordfence.com/threat-intel/vulnerabilities/id/935f5d76-d63a-4db4-b645-b7961ae8bfafhttps://nvd.nist.gov/vuln/detail/CVE-2026-3235

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C