CVE-2026-118048 · Package
NO FIX YET · SEE WHAT TO DO
The WP Data Access plugin for WordPress does not escape an autocomplete lookup label in Simple Form output, so stored HTML and script can be injected. When another user, including a higher-privileged one, opens the affected page, the script runs in their browser.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the WP Data Access plugin up to and including version 5.5.89 where subscriber-level users can edit lookup rows through a legacy Form. The flaw needs an authenticated account with that permission, and the payload fires for whoever later views the affected page, so administrators editing linked records are at risk. Sites without this plugin or without legacy Forms using autocomplete relationships can skip it.
Not affected if no-legacy-forms, no-subscriber-access, plugin-not-installed
Who cares self-hosted, wordpress, wp-data-access
5.5.89.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.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.