CVE-2025-14053

6.4 MEDIUM

📋 TL;DR

The Wish To Go WordPress plugin has a stored XSS vulnerability that allows authenticated attackers with Contributor access or higher to inject malicious scripts into website pages. These scripts execute whenever users view the compromised pages, potentially stealing credentials or performing unauthorized actions. All WordPress sites using Wish To Go plugin versions up to 0.5.2 are affected.

💻 Affected Systems

Products:
  • Wish To Go WordPress Plugin
Versions: All versions up to and including 0.5.2
Operating Systems: All operating systems running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Requires WordPress installation with Wish To Go plugin enabled. Contributor-level access or higher needed for exploitation.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator credentials, take over the WordPress site, install backdoors, deface the website, or redirect visitors to malicious sites.

🟠

Likely Case

Attackers with contributor access inject malicious scripts to steal user session cookies, perform actions as other users, or display phishing content.

🟢

If Mitigated

With proper user role management and security plugins, impact is limited to isolated script execution without privilege escalation.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires authenticated access but is technically simple once attacker has contributor privileges.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 0.5.3 or later

Vendor Advisory: https://plugins.trac.wordpress.org/browser/wish-to-go/trunk/wish-to-go.php

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find Wish To Go plugin. 4. Click 'Update Now' if update available. 5. If no update available, deactivate and delete plugin, then install fresh version from WordPress repository.

🔧 Temporary Workarounds

Disable Wish To Go Plugin

all

Temporarily deactivate the vulnerable plugin until patched version is available

wp plugin deactivate wish-to-go

Restrict User Roles

all

Limit contributor-level access to trusted users only

🧯 If You Can't Patch

  • Implement Content Security Policy (CSP) headers to restrict script execution
  • Use WordPress security plugins with XSS protection features like Wordfence or Sucuri

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel → Plugins → Installed Plugins → Wish To Go version. If version is 0.5.2 or lower, you are vulnerable.

Check Version:

wp plugin get wish-to-go --field=version

Verify Fix Applied:

After update, verify Wish To Go plugin version is 0.5.3 or higher in WordPress admin panel.

📡 Detection & Monitoring

Log Indicators:

  • Unusual shortcode modifications in post/page content
  • Multiple failed login attempts followed by successful contributor login
  • Suspicious script tags in post/page revisions

Network Indicators:

  • Unexpected external script loads from WordPress pages
  • Suspicious outbound connections when viewing specific pages

SIEM Query:

source="wordpress" AND (event="plugin_update" AND plugin="wish-to-go" AND version<="0.5.2") OR (event="post_edit" AND user_role="contributor" AND content CONTAINS "<script>")

🔗 References

📤 Share & Export