Running WP Data Access on your site? Check it against CVE-2026-118267 — free.
The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your WP Data Access is in the affected range (≤ 5.5.89), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.
Run the free mini-scan →The WP Data Access plugin for WordPress lets a site owner publish Data Apps — tables, forms and dashboards built on the site's database — with per-app rules about which rows and columns each audience may see and change. The read endpoints enforce those rules. The write endpoints, in versions up to and including 5.5.89, do not — and one of the columns a writer can reach is the administrator's password hash in wp_users. That is CVE-2026-118267, scoring CVSS 8.1, disclosed November 7, 2026 (CNA: Wordfence).
CVE-2026-118267 is an incorrect authorization vulnerability (CWE-863) in the WP Data Access – App Builder for Tables, Forms, Dashboards, Charts & Maps plugin (vendor: peterschulznl; wordpress.org slug wp-data-access, 10,000+ active installs at disclosure time). In November 2026 a public exploit template for this flaw appeared in ProjectDiscovery's Nuclei template index — the flaw is mass-scannable.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Network-reachable, no user interaction.wpda/app/update, wpda/app/delete, wpda/app/insert) pass attacker-supplied key and val parameters directly to the database update, delete and insert calls, without enforcing the container's row-filter (defaultWhere) or per-column allow-list (isSelected) restrictions that are correctly applied on the read endpoints. An attacker can therefore write to arbitrary rows and columns outside the configured restrictions — including overwriting the user_pass field of the administrator account in wp_users — and subsequently authenticate as the administrator: full site takeover.Check wp-admin → Plugins for WP Data Access and its version. At 5.5.89 or below and with a published Data App that enables update, delete or insert transactions for Subscriber-level or anonymous users, you are in the exposed configuration. A site running the plugin without a write-enabled published app is not reachable through this path — the precondition is carried here, not buried.
Our scanner checks it: run the free mini-scan, or check just this plugin at /tools/plugin-check?slug=wp-data-access. The check reads the version your site announces and flags 5.5.89 and below. A version above 5.5.89 earns no "patched" claim from us, though — the CVE record names no fixed version, so the check stays silent above the affected range rather than calling any release the fix. The version read also cannot see your Data Apps: whether a write-enabled app is published, and for whom, is yours to confirm.
user_pass — if an admin password changed and nobody remembers changing it, treat the account as compromised.Authorization enforced on the read path and forgotten on the write path is the same bug wearing two hats. The plugin's data layer knew the rules — the row filter and the column allow-list existed and worked — but each endpoint applied them by hand, and the write endpoints were the ones nobody remembered to guard. The check belongs in the data layer every endpoint shares, not in whichever endpoint someone happened to be looking at. When an AI builder (or a plugin author) wires up "view" and "edit" as separate features, the review question is always the same: does the write path pass through the exact same authorization code as the read path — or does it just look similar?
Related: WordPress Hardening for AI-Built Sites — the standing version of this discipline. How to Check If Your Web App Is Hacked — the follow-up pass if the audit finds an account you do not recognize.
Running WordPress with WP Data Access? Update to the latest release today, review your published Data Apps, then run the free check at preshipit.com/free-scan — our scanner checks it, version-checking this plugin against CVE-2026-118267 from the version your site announces to the world.
Check WP Data Access on your own site — free.
Our free WordPress Plugin Vulnerability Checker pulls WP Data Access's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-118267 included. No scan, no account.
Open the free plugin checker →The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.
New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.
Running WP Data Access on your site? Check it against CVE-2026-118267 — free.
The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your WP Data Access is in the affected range (≤ 5.5.89), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.
Run the free mini-scan →← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report