CVE-2024-10847

6.4 MEDIUM

📋 TL;DR

The Storely WordPress theme has a stored cross-site scripting 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 Storely theme versions up to 16.6 are affected.

💻 Affected Systems

Products:
  • Storely WordPress Theme
Versions: All versions up to and including 16.6
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Requires WordPress installation with Storely theme active. Contributor-level access or higher needed for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator credentials, take over the WordPress site, deface pages, redirect users to malicious sites, or install backdoors for persistent access.

🟠

Likely Case

Attackers with contributor accounts inject malicious JavaScript to steal user session cookies, redirect visitors to phishing pages, or display unwanted advertisements.

🟢

If Mitigated

With proper input validation and output escaping, the vulnerability is prevented, though contributor accounts could still be compromised through other means.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires authenticated access but is straightforward once an attacker has contributor-level credentials.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Version 16.7 or later

Vendor Advisory: https://wordpress.org/themes/storely/

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Appearance > Themes. 3. Find Storely theme and click 'Update Now' if available. 4. If automatic update not available, download latest version from WordPress.org and manually update.

🔧 Temporary Workarounds

Remove Contributor Role Access

all

Temporarily restrict contributor-level users from accessing the site until patching is complete.

Install Security Plugin with XSS Protection

all

Use WordPress security plugins like Wordfence or Sucuri that can detect and block XSS attempts.

🧯 If You Can't Patch

  • Implement strict input validation and output escaping for display name fields in custom code
  • Regularly audit user accounts and remove unnecessary contributor-level access

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel > Appearance > Themes > Storely theme details for version number. If version is 16.6 or lower, you are vulnerable.

Check Version:

wp theme list --field=name,version --status=active

Verify Fix Applied:

After updating, verify Storely theme version is 16.7 or higher in WordPress admin panel.

📡 Detection & Monitoring

Log Indicators:

  • Unusual display name changes by contributor users
  • JavaScript injection patterns in user profile updates

Network Indicators:

  • Unexpected JavaScript loading from user profile pages
  • Suspicious script tags in page responses

SIEM Query:

source="wordpress" AND (event="profile_update" OR event="user_modified") AND (field="display_name" OR field="user_nicename") AND value MATCHES "<script>"

🔗 References

📤 Share & Export