CVE-2024-12699
📋 TL;DR
The Service Box plugin for WordPress has a stored XSS vulnerability that allows authenticated attackers with Contributor-level access or higher to inject malicious scripts into pages. These scripts execute whenever users view the compromised pages, potentially affecting all visitors to vulnerable WordPress sites.
💻 Affected Systems
- Service Box WordPress Plugin
⚠️ 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.
- Review the CVE details at NVD
- Check vendor security advisories for your specific version
- Test if the vulnerability is exploitable in your environment
- Consider updating to the latest version as a precaution
⚠️ Risk & Real-World Impact
Worst Case
Attackers could steal session cookies, redirect users to malicious sites, deface websites, or perform actions on behalf of authenticated users, potentially leading to complete site compromise.
Likely Case
Attackers with contributor access inject malicious scripts to steal admin cookies or session tokens, leading to privilege escalation and further site compromise.
If Mitigated
With proper user access controls and content security policies, impact is limited to defacement or limited data exposure from the specific compromised pages.
🎯 Exploit Status
Exploitation requires authenticated access but is straightforward once attacker has contributor privileges.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Version 2.0 or later
Vendor Advisory: https://wordpress.org/plugins/service-boxs/#developers
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find Service Box plugin. 4. Click 'Update Now' if update available. 5. If no update available, deactivate and delete plugin, then install fresh version 2.0+ from WordPress repository.
🔧 Temporary Workarounds
Disable Service Box Plugin
allTemporarily disable the vulnerable plugin until patched
wp plugin deactivate service-boxs
Restrict User Roles
allTemporarily remove Contributor role access or restrict to trusted users only
🧯 If You Can't Patch
- Implement Content Security Policy (CSP) headers to restrict script execution
- Enable WordPress security plugins with XSS protection features
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin → Plugins → Installed Plugins → Service Box version. If version is 1.9 or earlier, system is vulnerable.
Check Version:
wp plugin get service-boxs --field=version
Verify Fix Applied:
Verify Service Box plugin version is 2.0 or later in WordPress admin panel.
📡 Detection & Monitoring
Log Indicators:
- Unusual content modifications by contributor-level users
- Suspicious script tags in page content
Network Indicators:
- Unexpected external script loads from WordPress pages
- Suspicious outbound connections from user browsers
SIEM Query:
source="wordpress.log" AND ("service-box" OR "contributor") AND ("script" OR "inject" OR "malicious")
🔗 References
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3216752%40service-boxs&new=3216752%40service-boxs&sfp_email=&sfph_mail=
- https://wordpress.org/plugins/service-boxs/#developers
- https://www.wordfence.com/threat-intel/vulnerabilities/id/e6a65630-0852-4ffc-8c23-295be95bd7f0?source=cve