WP Data Access

WP Data Access through 5.5.81 allows unauthenticated attacker-controlled input to reach an unsafe database query. Exploitation can expose database contents and disrupt database-backed site functionality.

WP Data Access through 5.5.68 checks access against attacker-controlled app_id but retrieves data using cnt_id without verifying that the container belongs to that app. An unauthenticated attacker can exploit the identifier mismatch to read data from protected app containers.

WP Data Access <= 5.5.80 fails to enforce authorization on an operation reachable by an unauthenticated attacker. The CVSS vector assigns confidentiality (high); the precise read or write.

WP Data Access is affected by cross-site scripting. Exploitation requires an authenticated author account. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is n/a through 5.5.79.

WP Data Access before 5.5.79 accepts attacker-selected column names through an unauthenticated AJAX action used by an affected front-end form. The action's nonce does not cover those column names, so an unauthenticated attacker can read arbitrary columns from the table bound to the form. If the form is bound to the WordPress users table, the exposed data can include password hashes.

An unauthenticated visitor can submit attacker-controlled content that WP Data Access 5.5.79 and earlier renders without sufficient output encoding.

WP Data Access is affected by SQL injection. The vulnerable path is reachable without authentication. A successful request can alter database queries and expose or modify WordPress data. The published affected range is n/a through 5.5.70.

WP Data Access is affected by cross-site scripting. Exploitation requires an authenticated contributor account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

WP Data Access is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

WP Data Access is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.

WP Data Access is affected by privilege escalation or authentication bypass. Exploitation requires an authenticated WordPress account. A successful request can grant permissions or access that the caller should not possess.

WP Data Access is affected by SQL injection. Exposure depends on how the affected operation is made reachable by the site. A successful request can alter database queries and expose or modify WordPress data.