CVE-2026-116551 · Package
NO FIX YET
The WP Customer Area plugin for WordPress does not sanitize the 'display_name' field, so text entered there is saved and later shown to other users without escaping. An attacker with a subscriber account can plant JavaScript that runs in the browser of anyone who opens an affected page.
first public Nov 6, 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 Customer Area plugin at version 8.4.0 or earlier where users can register or hold subscriber-level accounts. Sites without this plugin, or where only trusted administrators have accounts, face lower risk. The sources do not describe any configuration that changes exposure.
Not affected if no-subscriber-accounts, plugin-not-installed
Who cares self-hosted, wordpress, wp-customer-area
wp-content/plugins/8.4.0 as affectedNo fix yet, per the sources.
The WP Customer Area plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'display_name' parameter in all versions up to, and including, 8.4.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an 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.