Plugins · wp-data-access · data as of 2026-11-04
Is WP Data Access safe? Known vulnerabilities and latest version
- Latest version
- 5.5.90
- Last updated
- 2026-10-28
- Active installs
- 10,000+
- Known issues on record
- 19
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 7.4+
Turn your data into WordPress apps. No code required. Tables, forms, dashboards, charts, maps, optional hooks for developers, 35+ languages. — by Passionate Programmer Peter
What to do
- Update to the latest version (5.5.90). Anything older than 5.5.89 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get wp-data-access --field=version shows what you run; wp plugin update wp-data-access updates it.
Check your version
Known vulnerabilities
19 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 5.9 CVE-2026-110023 · published 2026-10-31
Information disclosure in WP Data Access (5.5.88 and older)
- Affected
- 5.5.88 and older
- Fixed in
- 5.5.89 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The WP Data Access – App Builder for Tables, Forms, Dashboards, Charts & Maps plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 5.5.88 via the 'rel_tab' parameter. This makes it possible for unauthenticated attackers to extract every row and column of the underlying database table backing any anonymously published app, including WordPress user password hashes, email addresses, and password-reset keys from wp_users. Exploitation requires that an administrator has published at least one app with its REST API authorization set to 'anonymous', which is the standard configuration for publicly embedded apps.
NVD CVE-2026-110023Wordfence advisoryCode change (fix)Plugin source
medium 5.0 CVE-2026-106470 · published 2026-10-17
Cross-site request forgery (CSRF) in WP Data Access (older than 5.5.88)
- Affected
- older than 5.5.88
- Fixed in
- 5.5.88
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The WP Data Access WordPress plugin before 5.5.88 does not have authorisation and CSRF checks in one of its actions, allowing any authenticated user, such as a subscriber, to make the server open connections to arbitrary hosts and ports, including internal ones, and read back the outcome.
medium 5.3 CVE-2026-106098 · published 2026-10-14
Missing authorization check in WP Data Access (older than 5.5.77)
- Affected
- older than 5.5.77
- Fixed in
- 5.5.77
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
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.
medium 5.3 CVE-2026-106099 · published 2026-10-14
Information disclosure in WP Data Access (older than 5.5.84)
- Affected
- older than 5.5.84
- Fixed in
- 5.5.84
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The WP Data Access WordPress plugin before 5.5.84 does not restrict its database table export action to authorized users, gating it only with a token that the WP Data Access WordPress plugin before 5.5.84 itself prints into the public pages on which it displays a table, allowing unauthenticated attackers to export the complete contents of any publicly displayed table, including columns and rows withheld from the display shown to visitors.
critical 9.3 CVE-2026-95605 · published 2026-10-07
SQL injection in WP Data Access (5.5.82 and older)
- Affected
- 5.5.82 and older
- Fixed in
- 5.5.83
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Passionate Programmer Peter WP Data Access allows Blind SQL Injection. This issue affects WP Data Access: from n/a through 5.5.82.
high 8.2 CVE-2026-93621 · published 2026-09-30
SQL injection in WP Data Access (5.5.84 and older)
- Affected
- 5.5.84 and older
- Fixed in
- 5.5.85
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Unauthenticated SQL Injection in WP Data Access <= 5.5.84 versions.
critical 9.3 CVE-2026-81293 · published 2026-08-31
SQL injection in WP Data Access (5.5.81 and older)
- Affected
- 5.5.81 and older
- Fixed in
- 5.5.82
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Unauthenticated SQL Injection in WP Data Access <= 5.5.81 versions.
medium 5.3 CVE-2026-3235 · published 2026-08-26
Missing authorization check in WP Data Access (5.5.68 and older)
- Affected
- 5.5.68 and older
- Fixed in
- 5.5.69 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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).
NVD CVE-2026-3235Wordfence advisoryCode change (fix)Plugin source
medium 5.9 CVE-2026-66595 · published 2026-08-20
Missing authorization check in WP Data Access (5.5.80 and older)
- Affected
- 5.5.80 and older
- Fixed in
- 5.5.81
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Unauthenticated Broken Access Control in WP Data Access <= 5.5.80 versions.
medium 5.9 CVE-2026-73344 · published 2026-08-13
Cross-site scripting (XSS) in WP Data Access (5.5.79 and older)
- Affected
- 5.5.79 and older
- Fixed in
- 5.5.80
- Access needed (per CVSS)
- Needs an admin-level account; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Author Cross Site Scripting (XSS) in WP Data Access <= 5.5.79 versions.
high 7.5 CVE-2026-18032 · published 2026-08-09
Information disclosure in WP Data Access (older than 5.5.79)
- Affected
- older than 5.5.79
- Fixed in
- 5.5.79
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The WP Data Access WordPress plugin before 5.5.79 does not validate the column names it accepts on one of its unauthenticated AJAX actions, and the nonce guarding that action does not cover them, allowing unauthenticated attackers to read arbitrary columns of the database table the affected front-end form is bound to, including user password hashes where that table is the users table.
high 7.1 CVE-2026-66663 · published 2026-08-06
Cross-site scripting (XSS) in WP Data Access (5.5.79 and older)
- Affected
- 5.5.79 and older
- Fixed in
- 5.5.80
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Unauthenticated Cross Site Scripting (XSS) in WP Data Access <= 5.5.79 versions.
critical 9.3 CVE-2026-42665 · published 2026-06-15
SQL injection in WP Data Access (5.5.70 and older)
- Affected
- 5.5.70 and older
- Fixed in
- 5.5.71
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Unauthenticated SQL Injection in WP Data Access <= 5.5.70 versions.
medium 6.4 CVE-2026-0557 · published 2026-02-14
Stored cross-site scripting (XSS) in WP Data Access (5.5.63 and older)
- Affected
- 5.5.63 and older
- Fixed in
- 5.5.64 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The WP Data Access plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'wpda_app' shortcode in all versions up to, and including, 5.5.63 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
medium 6.5 CVE-2025-39582 · published 2025-04-16
Cross-site scripting (XSS) in WP Data Access (5.5.36 and older)
- Affected
- 5.5.36 and older
- Fixed in
- 5.5.37
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Passionate Programmer Peter WP Data Access wp-data-access allows DOM-Based XSS.This issue affects WP Data Access: from n/a through <= 5.5.36.
high 7.5 CVE-2024-12428 · published 2024-12-25
SQL injection in WP Data Access (5.5.22 and older)
- Affected
- 5.5.22 and older
- Fixed in
- 5.5.23 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The WP Data Access – App, Table, Form and Chart Builder plugin plugin for WordPress is vulnerable to SQL Injection via the 'order[user_login][dir]' parameter in all versions up to, and including, 5.5.22 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
medium 4.3 CVE-2024-43295 · published 2024-08-26
Cross-site request forgery (CSRF) in WP Data Access (5.5.7 and older)
- Affected
- 5.5.7 and older
- Fixed in
- 5.5.9
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Cross-Site Request Forgery (CSRF) vulnerability in Passionate Programmers B.V. WP Data Access.This issue affects WP Data Access: from n/a through 5.5.7.
high 8.8 CVE-2023-1874 · published 2023-04-12
Privilege escalation in WP Data Access (5.3.7 and older)
- Affected
- 5.3.7 and older
- Fixed in
- 5.3.8 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The WP Data Access plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 5.3.7. This is due to a lack of authorization checks on the multiple_roles_update function. This makes it possible for authenticated attackers, with minimal permissions such as a subscriber, to modify their user role by supplying the 'wpda_role[]' parameter during a profile update. This requires the 'Enable role management' setting to be enabled for the site.
NVD CVE-2023-1874Wordfence advisoryWordfence advisorypacketstormsecurity.comPlugin source
critical 9.8 CVE-2021-24866 · published 2021-12-06
SQL injection in WP Data Access (older than 5.0.0)
- Affected
- older than 5.0.0
- Fixed in
- 5.0.0
- Access needed (per CVSS)
- No login needed
- Range from
- NVD analysis · score by NVD
Details from the advisory
The WP Data Access WordPress plugin before 5.0.0 does not properly sanitise and escape the backup_date parameter before using it a SQL statement, leading to a SQL injection issue and could allow arbitrary table deletion
Recent activity
- 2026-10-28 — latest release on wordpress.org (5.5.90).
- 2026-10-31 — Information disclosure disclosed (CVE-2026-110023), fixed in 5.5.89.
- 2026-10-17 — Cross-site request forgery (CSRF) disclosed (CVE-2026-106470), fixed in 5.5.88.
- 2026-10-14 — Missing authorization check disclosed (CVE-2026-106098), fixed in 5.5.77.
Get an email when WP Data Access has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for WP Data Access (wp-data-access) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: SQL injection (6) · Cross-site scripting (XSS) (4) · Sensitive data exposure (3) · Missing authorization (3) · Cross-site request forgery (CSRF) (2) · Privilege escalation (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/wp-data-access (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/wp-data-access"><img src="https://laskyr.com/plugins/wp-data-access/badge.svg" alt="WP Data Access vulnerability status"></a>