CVE-2026-2722
Received Received - Intake
Stored XSS in WordPress Stock Ticker Plugin Allows Admin Script Injection

Publication date: 2026-03-07

Last updated on: 2026-03-07

Assigner: Wordfence

Description
The Stock Ticker plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 3.26.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-07
Last Modified
2026-03-07
Generated
2026-05-07
AI Q&A
2026-03-07
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wpau stock_ticker to 3.26.1 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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 Stock Ticker plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) in all versions up to and including 3.26.1. This vulnerability arises because the plugin does not properly sanitize input or escape output in its admin settings. As a result, authenticated users with administrator-level permissions or higher can inject arbitrary web scripts into pages. These scripts execute whenever a user accesses the injected page. 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 allows attackers with administrator-level access to inject malicious scripts into the WordPress site. These scripts can execute in the context of other users visiting the affected pages, potentially leading to theft of sensitive information such as cookies or credentials, session hijacking, or performing actions on behalf of other users. Since the vulnerability is a Stored Cross-Site Scripting, the malicious code persists on the site and affects all users who view the injected content. However, exploitation requires the attacker to have administrator-level permissions and the site to be a multi-site installation or have unfiltered_html disabled.


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?

The vulnerability in the Stock Ticker WordPress plugin is a Stored Cross-Site Scripting (XSS) issue that requires administrator-level permissions to exploit and affects multi-site installations or those with unfiltered_html disabled.

Detection involves checking if the vulnerable plugin version (up to and including 3.26.1) is installed on your WordPress multi-site setup and whether unfiltered_html is disabled.

Since the vulnerability is related to stored XSS via admin settings, detection can include:

  • Verifying the plugin version installed by running a command to list WordPress plugins and their versions, for example using WP-CLI: `wp plugin list --format=json`
  • Checking if the site is a WordPress multi-site installation by inspecting the WordPress configuration or using WP-CLI: `wp site list`
  • Reviewing the admin settings pages of the Stock Ticker plugin for suspicious or unexpected script content injected in the settings fields.
  • Monitoring HTTP traffic for suspicious script payloads in pages generated by the plugin, especially those accessible by authenticated users.

No specific detection commands or automated scanning scripts are provided in the available resources.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include:

  • Upgrade the Stock Ticker plugin to version 3.26.2 or later, where the vulnerability has been fixed by improving input validation and sanitization.
  • Restrict administrator-level access to trusted users only, since exploitation requires authenticated admin permissions.
  • If upgrading immediately is not possible, consider disabling the plugin or restricting its usage on multi-site installations or where unfiltered_html is disabled.
  • Review and sanitize any existing plugin settings to remove potentially injected scripts.
  • Monitor logs and user activity for suspicious behavior related to the plugin.

Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart