CVE-2026-1247
Stored XSS in WordPress Survey Plugin Affects Multi-Site Admins
Publication date: 2026-03-21
Last updated on: 2026-03-21
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordfence | survey_plugin | to 1.1 (inc) |
| seos | survey | to 1.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Survey plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in all versions up to and including 1.1. This vulnerability arises because the plugin does not properly sanitize input or escape output in the admin settings. As a result, authenticated users with administrator-level permissions or higher can inject malicious web scripts into pages. These scripts execute whenever any user accesses the affected pages.
This vulnerability specifically affects multi-site WordPress installations and installations where the unfiltered_html capability has been disabled.
How can this vulnerability impact me? :
This vulnerability can allow attackers with administrator-level access to inject malicious scripts into the website. These scripts can execute in the browsers of users who visit the injected pages, potentially leading to theft of sensitive information, session hijacking, or other malicious actions.
Because the vulnerability requires high privileges (administrator-level) and affects multi-site or restricted HTML installations, the risk is somewhat limited but still significant in those environments.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know