Unknown WP Data Access vulnerabilities

5 vulnerabilities

Known vulnerabilities in Unknown WP Data Access, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.

5CVE-2026-106470unknownwp data access
EPSS score
0.11%
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.5.3CVE-2026-106099unknownwp data access
EPSS score
0.27%
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.5.3CVE-2026-106098unknownwp data access
EPSS score
0.24%
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.9.8CVE-2021-24866unknownwp data access+2
EPSS score
1.63%
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 deletion7.5CVE-2026-18032unknownwp data access+1
EPSS score
0.43%
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.