HomeWordPress vulnerabilitiesWP Data Access
WP Data Access vulnerabilities
WP Data Access has 19 known vulnerabilities in this database. The most recent published record is dated 21 Nov 2026.
- Known vulnerabilities
- 19
- Active installs
- 10,000+
- Latest version
- 5.5.92
- Last updated
- 6 Nov 2026
- Most recent
- 21 Nov 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-124214 | Medium 5.4 | Up to 5.5.92 | No fixed version yet | 1 d ago |
| SQL injection CVE-2026-125832 | High 8.5 | Up to 5.5.92 | No fixed version yet | 7 d ago |
| Privilege escalation CVE-2026-118267 | High 8.1 | Up to 5.5.89 | Fixed in a later version (latest 5.5.92) | 7 Nov 2026 |
| Cross-site request forgery (CSRF) CVE-2026-121783 | Medium 6.5 | Up to 5.5.90 | Fixed in a later version (latest 5.5.92) | 7 Nov 2026 |
| Cross-site scripting (XSS) CVE-2026-120479 | Medium 6.4 | Up to 5.5.90 | Fixed in a later version (latest 5.5.92) | 7 Nov 2026 |
| Cross-site scripting (XSS) CVE-2026-118204 | Medium 6.4 | Up to 5.5.89 | Fixed in a later version (latest 5.5.92) | 7 Nov 2026 |
| SQL injection CVE-2026-121536 | Medium 5.3 | Up to 5.5.90 | Fixed in a later version (latest 5.5.92) | 7 Nov 2026 |
| Cross-site scripting (XSS) CVE-2026-118048 | Medium 6.4 | Up to 5.5.89 | Fixed in a later version (latest 5.5.92) | 7 Nov 2026 |
| Broken access control CVE-2026-110023 | Medium 5.9 | Up to 5.5.88 | Fixed in a later version (latest 5.5.92) | 31 Oct 2026 |
| Cross-site request forgery (CSRF) CVE-2026-106470 | Medium 5.0 | Before 5.5.88 | Fixed in 5.5.88 | 17 Oct 2026 |
| Sensitive data exposure CVE-2026-106099 | Medium 5.3 | Before 5.5.84 | Fixed in 5.5.84 | 14 Oct 2026 |
| Broken access control CVE-2026-106098 | Medium 5.3 | Before 5.5.77 | Fixed in 5.5.77 | 14 Oct 2026 |
| SQL injection CVE-2026-95605 | Critical 9.3 | Up to 5.5.82 | Fixed in a later version (latest 5.5.92) | 7 Oct 2026 |
| Broken access control CVE-2026-3235 | Medium 5.3 | Up to 5.5.68 | Fixed in a later version (latest 5.5.92) | 26 Aug 2026 |
| Sensitive data exposure CVE-2026-18032 | High 7.5 | Before 5.5.79 | Fixed in 5.5.79 | 9 Aug 2026 |
| Cross-site scripting (XSS) CVE-2026-0557 | Medium 6.4 | Up to 5.5.63 | Fixed in a later version (latest 5.5.92) | 14 Feb 2026 |
| SQL injection CVE-2024-12428 | High 7.5 | Up to 5.5.22 | Fixed in a later version (latest 5.5.92) | 25 Dec 2024 |
| Privilege escalation CVE-2023-1874 | High 7.5 | Up to 5.3.7 | Fixed in a later version (latest 5.5.92) | 12 Apr 2023 |
| SQL injection CVE-2021-24866 | Critical 9.8 | Before 5.0.0 | Fixed in 5.0.0 | 6 Dec 2021 |
Read the published descriptions
- CVE-2026-124214, 21 Nov 2026
- The WP Data Access - App Builder for Tables, Forms, Dashboards, Charts & Maps plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'HyperlinkObject.label (percent-encoded)' parameter in all versions up to, and including, 5.5.92 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the WordPress site to have a published Anonymous-access Registration Form app configured against a table with a HyperlinkObject column, and a legacy Data Project list using a $$link$$ Dynamic Hyperlink against that same column; given this configuration, any unauthenticated visitor can plant the payload. CVE record
- CVE-2026-125832, 15 Nov 2026
- Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Passionate Programmer Peter WP Data Access wp-data-access allows SQL Injection.This issue affects WP Data Access: from n/a through 5.5.92. CVE record
- CVE-2026-118267, 7 Nov 2026
- The WP Data Access - App Builder for Tables, Forms, Dashboards, Charts & Maps plugin for WordPress is vulnerable to Incorrect Authorization leading to Privilege Escalation in all versions up to, and including, 5.5.89 This is due to the plugin's write endpoints (`wpda/app/update`, `wpda/app/delete`, `wpda/app/insert`) passing the attacker-supplied `key` and `val` parameters directly to `$wpdadb->update`, `$wpdadb->delete`, and `$wpdadb->insert` without enforcing the container's row-filter (`defaultWhere`) or per-column allow-list (`isSelected`) restrictions that are correctly applied on the read endpoints. This makes it possible for authenticated attackers, with Subscriber-level access and above, to write to arbitrary rows and columns outside the configured restrictions - including overwriting the `user_pass` field of the WordPress administrator account in `wp_users` - and subsequently authenticate as the administrator, achieving full site takeover. Exploitation requires an administrator to have published a Data App that enables write transactions (update, delete, or insert) for Subscriber-level or anonymous users, which is an explicitly advertised use-case of the plugin. Exploitation by unauthenticated attackers requires that the administrator has published a Data App whose rest_api.authorization is 'anonymous' and whose container has transactions.update (or delete/insert) enabled. On a default installation, where that is not configured, the vulnerability requires attackers with subscriber-level access and above. CVE record
- CVE-2026-121783, 7 Nov 2026
- Cross-Site Request Forgery (CSRF) vulnerability in Passionate Programmer Peter WP Data Access wp-data-access allows Cross Site Request Forgery.This issue affects WP Data Access: from n/a through 5.5.90. CVE record
- CVE-2026-120479, 7 Nov 2026
- The WP Data Access - App Builder for Tables, Forms, Dashboards, Charts & Maps plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Data Projects front-end simple form in versions up to, and including, 5.5.90 This is due to insufficient input sanitization and output escaping on the value of TEXT/TINYTEXT/MEDIUMTEXT/LONGTEXT columns rendered by the WPDA_Simple_Form_Item_Textarea::show_item() method, which emits the stored column value directly inside a <textarea> element after only replacing '&' with '&'. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2026-118204, 7 Nov 2026
- The WP Data Access - App Builder for Tables, Forms, Dashboards, Charts & Maps plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'ImageURL column value (populated from wp_usermeta.description in the demonstrated path)' parameter in all versions up to, and including, 5.5.89 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires an administrator to have published a DataTables shortcode over a database column the attacker controls (e.g., wp_usermeta.description) with the Image URL media type assigned to that column - both are supported plugin features but are not enabled by default. CVE record
- CVE-2026-121536, 7 Nov 2026
- The WP Data Access - App Builder for Tables, Forms, Dashboards, Charts & Maps plugin for WordPress is vulnerable to generic SQL Injection via the 'engine' parameter in all versions up to, and including, 5.5.90 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This is only exploitable when an administrator has configured a Data Project page to admit a lower-privileged role, which is the plugin's documented mechanism for sharing projects with subscribers and other users. CVE record
- CVE-2026-118048, 7 Nov 2026
- The WP Data Access plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Simple Form autocomplete lookup label in versions up to, and including, 5.5.89 This is due to insufficient output escaping on the value returned by WPDA_Autocomplete::autocomplete_lookup() when it is emitted into a single-quoted HTML attribute by WPDA_Simple_Form_Item_Autocomplete::show_item() (the escape-output lint is explicitly suppressed on the echo line). This makes it possible for authenticated attackers, with Subscriber-level access and above, who are permitted to edit a lookup row through a legacy Form, to inject arbitrary web scripts in pages that will execute whenever a user - including a higher-privileged user editing a linked record that uses the autocomplete relationship - accesses the injected page. CVE record
- CVE-2026-110023, 31 Oct 2026
- 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. CVE record
- CVE-2026-106470, 17 Oct 2026
- 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. CVE record
- CVE-2026-106099, 14 Oct 2026
- 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. CVE record
- CVE-2026-106098, 14 Oct 2026
- 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. CVE record
- CVE-2026-95605, 7 Oct 2026
- 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. CVE record
- CVE-2026-3235, 26 Aug 2026
- 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). CVE record
- CVE-2026-18032, 9 Aug 2026
- 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. CVE record
- CVE-2026-0557, 14 Feb 2026
- 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. CVE record
- CVE-2024-12428, 25 Dec 2024
- 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. CVE record
- CVE-2023-1874, 12 Apr 2023
- 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. CVE record
- CVE-2021-24866, 6 Dec 2021
- 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 CVE record
What to do if you run WP Data Access
If you run WP Data Access, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WP Data Access vulnerabilities
Free. We email you when a new vulnerability is published for WP Data Access, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.