CVE-2025-14053
Stored XSS in Wish To Go WordPress Plugin via Shortcode Attributes
Publication date: 2026-01-07
Last updated on: 2026-01-07
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wish_to_go | wish_to_go | to 0.5.2 (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 Wish To Go plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in all versions up to 0.5.2. This occurs because the plugin does not properly sanitize or escape user-supplied shortcode attributes. As a result, authenticated users with Contributor-level access or higher can inject malicious scripts into pages. These scripts execute whenever any user views the infected page.
How can this vulnerability impact me? :
This vulnerability allows attackers with Contributor-level access or higher to inject arbitrary scripts into WordPress pages. These scripts can execute in the browsers of users who visit the affected pages, potentially leading to theft of user credentials, session hijacking, defacement, or other malicious actions. It compromises the integrity and security of the website and its users.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves identifying WordPress sites running the Wish To Go plugin version 0.5.2 or earlier and checking for shortcode attributes that may contain malicious scripts. Since the vulnerability is a Stored Cross-Site Scripting via shortcode attributes, you can scan the WordPress database for posts or pages containing the shortcodes [wishwidget], [travelplanwidget], [wishcounterwidget], or [sharetripwidget] with suspicious or script-like attribute values. Commands to detect this might include using WP-CLI to search post content or meta fields for suspicious shortcode attributes. For example, you can run a WP-CLI command to search posts containing these shortcodes and inspect their attributes for script tags or suspicious payloads. Example command: wp db query "SELECT ID, post_content FROM wp_posts WHERE post_content LIKE '%[wishwidget%' OR post_content LIKE '%[travelplanwidget%' OR post_content LIKE '%[wishcounterwidget%' OR post_content LIKE '%[sharetripwidget%'". Additionally, monitoring HTTP requests for unusual script execution or alerts from web application firewalls when these shortcodes are rendered may help detect exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the Wish To Go plugin to a version later than 0.5.2 where the vulnerability is fixed, if available. If an update is not yet available, restrict Contributor-level and higher users from adding or editing shortcodes with attributes until a patch is applied. Additionally, implement input sanitization and output escaping manually or via security plugins to prevent script injection through shortcode attributes. As a temporary measure, disable or remove the Wish To Go plugin to prevent exploitation. Monitoring and restricting user permissions to trusted users only can also reduce risk. [1]