WP Site Protect <= 1.0 - Cross-Site Scripting
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- WP Site Protect
- Affected Version
<= 1.0- CVSS
- 7.1High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE pending
At a glance
This record tracks a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP Site Protect WordPress plugin, affecting versions <= 1.0. It carries a CVSS score of 7.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed December 2017.
Vulnerability Overview
The WP Site Protect plugin for WordPress is vulnerable to Cross-Site Scripting via the 'password' parameter in versions up to, and including, 1.0 due to insufficient input sanitization and output escaping. This makes it possible for attackers to inject arbitrary web scripts that execute in a victim's browser. The author of this plugin has fixed this issue in GitHub, but not in the WordPress plugin repository.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
WP Site Protect <= 1.0 carries this weakness at password, and reaching it takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. No fixed build of this plugin is recorded for WP Site Protect yet, so installs running <= 1.0 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP Site Protect: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C