CVE-2025-14113
Unknown Unknown - Not Provided
Stored XSS in Viitor Button Shortcodes Plugin Allows Script Injection

Publication date: 2026-01-07

Last updated on: 2026-01-07

Assigner: Wordfence

Description
The Viitor Button Shortcodes plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'link' shortcode attribute in all versions up to, and including, 3.0.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-07
Last Modified
2026-01-07
Generated
2026-05-07
AI Q&A
2026-01-07
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
viitor viitor_button_shortcodes to 3.0.0 (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?

This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the Viitor Button Shortcodes WordPress plugin. It occurs because the plugin does not properly sanitize or escape the 'link' shortcode attribute, allowing authenticated users with Contributor-level access or higher to inject malicious scripts. These scripts are then stored and executed whenever any user views the affected page. [1]


How can this vulnerability impact me? :

An attacker with Contributor-level access or higher can exploit this vulnerability to inject arbitrary JavaScript into pages. This can lead to session hijacking, defacement, or redirection to malicious sites, potentially compromising user data and site integrity. Since the scripts execute in the context of users visiting the injected pages, it can affect any user accessing those pages. [1]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

To detect this vulnerability, you can scan your WordPress installation for the presence of the Viitor Button Shortcodes plugin version 3.0.0 or earlier. Additionally, you can search for usage of the 'link' shortcode attribute in posts or pages that might contain malicious scripts. Since the vulnerability involves stored cross-site scripting via shortcode attributes, inspecting the database for suspicious shortcode content or using WordPress CLI commands to search posts for the shortcode usage can help. For example, you can use the following WP-CLI command to search posts for the shortcode: wp post list --post_type=post --format=ids | xargs -I % wp post get % --field=post_content | grep '\[ww_vcsc_boxes.*link=.*<script' to find posts with potentially malicious script injections in the 'link' attribute. Network detection might involve monitoring HTTP responses for injected scripts in pages using this shortcode. However, no specific detection commands are provided in the resources. [1]


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The provided resources do not contain information regarding the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include updating the Viitor Button Shortcodes plugin to a version later than 3.0.0 where the vulnerability is fixed. If an update is not available, temporarily disabling or removing the plugin will prevent exploitation. Additionally, review and sanitize any existing shortcode content that uses the 'link' attribute to remove malicious scripts. Restrict Contributor-level and higher user permissions to trusted users only, as the vulnerability requires authenticated users with at least Contributor access. Monitoring and applying input sanitization and output escaping in shortcode handling can also mitigate risks. [1]


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