WP Data Access Plugin up to 5.5.78 on WordPress information disclosure

Summaryinfo

A vulnerability identified as problematic has been detected in WP Data Access Plugin up to 5.5.78. Impacted is an unknown function. Performing a manipulation results in information disclosure. This vulnerability is cataloged as CVE-2026-18032. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in WP Data Access Plugin up to 5.5.78. It has been classified as problematic. This affects some unknown functionality. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:

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.

The advisory is shared at wpscan.com. This vulnerability is uniquely identified as CVE-2026-18032 since 07/28/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

Upgrading to version 5.5.79 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• WordPress Plugin

Name

• WP Data Access Plugin

Version

• 5.5.0
• 5.5.1
• 5.5.2
• 5.5.3
• 5.5.4
• 5.5.5
• 5.5.6
• 5.5.7
• 5.5.8
• 5.5.9
• 5.5.10
• 5.5.11
• 5.5.12
• 5.5.13
• 5.5.14
• 5.5.15
• 5.5.16
• 5.5.17
• 5.5.18
• 5.5.19
• 5.5.20
• 5.5.21
• 5.5.22
• 5.5.23
• 5.5.24
• 5.5.25
• 5.5.26
• 5.5.27
• 5.5.28
• 5.5.29
• 5.5.30
• 5.5.31
• 5.5.32
• 5.5.33
• 5.5.34
• 5.5.35
• 5.5.36
• 5.5.37
• 5.5.38
• 5.5.39
• 5.5.40
• 5.5.41
• 5.5.42
• 5.5.43
• 5.5.44
• 5.5.45
• 5.5.46
• 5.5.47
• 5.5.48
• 5.5.49
• 5.5.50
• 5.5.51
• 5.5.52
• 5.5.53
• 5.5.54
• 5.5.55
• 5.5.56
• 5.5.57
• 5.5.58
• 5.5.59
• 5.5.60
• 5.5.61
• 5.5.62
• 5.5.63
• 5.5.64
• 5.5.65
• 5.5.66
• 5.5.67
• 5.5.68
• 5.5.69
• 5.5.70
• 5.5.71
• 5.5.72
• 5.5.73
• 5.5.74
• 5.5.75
• 5.5.76
• 5.5.77
• 5.5.78

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion