CVE-2025-10135

6.4 MEDIUM

📋 TL;DR

The WP ViewSTL WordPress plugin has a stored XSS vulnerability that allows authenticated attackers with contributor-level 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 WP ViewSTL version 1.0 or earlier are affected.

💻 Affected Systems

Products:
  • WP ViewSTL WordPress Plugin
Versions: All versions up to and including 1.0
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Requires WordPress installation with WP ViewSTL plugin enabled. Contributor-level authentication required 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, deface websites, redirect users to malicious sites, or install backdoors for persistent access.

🟠

Likely Case

Attackers with contributor access inject malicious scripts to steal user session cookies or credentials, potentially compromising user accounts.

🟢

If Mitigated

With proper user access controls and content review processes, the impact is limited to potential defacement of specific pages.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Exploitation requires contributor-level WordPress access. Attackers need to create or edit posts/pages using the vulnerable shortcode.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Version after 1.0 (check plugin repository for latest)

Vendor Advisory: https://wordpress.org/plugins/wp-viewstl/

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find WP ViewSTL plugin. 4. Click 'Update Now' if update available. 5. If no update available, deactivate and delete plugin immediately.

🔧 Temporary Workarounds

Remove Contributor Access

all

Temporarily remove contributor-level access for untrusted users until patch is applied.

Disable Plugin

all

Deactivate WP ViewSTL plugin to prevent exploitation while awaiting patch.

🧯 If You Can't Patch

  • Immediately deactivate and remove the WP ViewSTL plugin from all WordPress installations.
  • Implement strict user access controls and review all posts/pages created by contributors for suspicious content.

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel > Plugins > Installed Plugins for WP ViewSTL version 1.0 or earlier.

Check Version:

wp plugin list --name=wp-viewstl --field=version

Verify Fix Applied:

Verify WP ViewSTL plugin is updated to version after 1.0 or completely removed from the system.

📡 Detection & Monitoring

Log Indicators:

  • Unusual post/page edits by contributor users
  • Suspicious shortcode usage in content
  • Multiple failed login attempts followed by content creation

Network Indicators:

  • Unexpected JavaScript loading from WordPress pages
  • Suspicious outbound connections after page views

SIEM Query:

source="wordpress" AND (event="post_edit" OR event="page_edit") AND user_role="contributor" AND content CONTAINS "[viewstl"

🔗 References

📤 Share & Export