CVE-2026-18032: WP Data Access · Information Exposure
Affects WP Data AccessSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 5.5.79 soon.
Data as of 7 Nov 2026, 23:24 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.5.79
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Upgrade WP Data Access to 5.5.79.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WP Data Access | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict access to the affected AJAX action if possible or monitor for suspicious activity related to this plugin. Avoid exposing sensitive tables through this plugin's front-end forms.
Description
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.