CVE-2025-11860

6.4 MEDIUM

📋 TL;DR

The Twitter Feed plugin for WordPress has a stored XSS vulnerability in versions up to 1.3.1. Authenticated attackers with contributor-level access can inject malicious scripts via the 'ottwitter_feed' shortcode parameters, which execute when users view affected pages. This affects all WordPress sites using the vulnerable plugin version.

💻 Affected Systems

Products:
  • Twitter Feed WordPress Plugin
Versions: All versions up to and including 1.3.1
Operating Systems: All operating systems running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Requires WordPress installation with the vulnerable plugin active. Contributor-level access or higher is 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 admin credentials, redirect users to malicious sites, deface websites, or install backdoors for persistent access.

🟠

Likely Case

Attackers with contributor access inject malicious scripts to steal user session cookies or perform phishing attacks against site visitors.

🟢

If Mitigated

With proper input validation and output escaping, the vulnerability is prevented, and only authenticated users with appropriate privileges can access administrative functions.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires authenticated access with contributor privileges or higher. The vulnerability is in publicly accessible code.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.3.2 or later

Vendor Advisory: https://plugins.trac.wordpress.org/browser/ot-twitter-feed/trunk/ottwitterfeed-shortcode.php

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find 'Twitter Feed' plugin. 4. Click 'Update Now' if update is available. 5. Alternatively, download version 1.3.2+ from WordPress plugin repository and manually update.

🔧 Temporary Workarounds

Remove vulnerable shortcode usage

all

Temporarily disable or remove usage of the 'ottwitter_feed' shortcode from posts/pages until patched.

Restrict user roles

all

Limit contributor-level access to trusted users only and implement principle of least privilege.

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block XSS payloads in shortcode parameters
  • Disable the Twitter Feed plugin completely until patching is possible

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel > Plugins > Installed Plugins for 'Twitter Feed' plugin version. If version is 1.3.1 or lower, you are vulnerable.

Check Version:

wp plugin list --name='twitter-feed' --field=version (if WP-CLI is installed)

Verify Fix Applied:

After updating, verify plugin version shows 1.3.2 or higher in WordPress admin plugins list.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests containing script tags in 'width' or 'height' parameters to WordPress pages
  • Multiple failed authentication attempts followed by successful contributor-level login

Network Indicators:

  • Outbound connections to suspicious domains from your WordPress site
  • Unexpected JavaScript execution in page responses

SIEM Query:

source="wordpress.log" AND ("ottwitter_feed" AND ("<script" OR "javascript:"))

🔗 References

📤 Share & Export