Comment Press <= 2.7.1 - Cross-Frame Scripting
Strategic Overview
- Status
- Patched in 2.7.2
- Affected Version
< 2.7.2- CVSS
- 4.7Medium
- 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 medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Comment System Plugin for WordPress & Ajax Comments - Comment Press WordPress plugin, affecting versions < 2.7.2. It carries a CVSS score of 4.7 (reachable over the network). Exploitation requires no authentication. The issue is fixed in version 2.7.2; sites on affected versions should update now. Disclosed October 2020, reported by R3N0.
Vulnerability Overview
The Comment Press plugin for WordPress is vulnerable to Cross-Frame Scripting in versions up to, and including, 2.7.1. This is due to the plugin not validating user supplied inputs. This makes it possible for unauthenticated attackers to exploit the vulnerability by tricking users to clicking on URL links that hides invisible iFrames and make it possible to steal credentials and take over the victim's machine.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Comment System Plugin for WordPress & Ajax Comments - Comment Press < 2.7.2 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. For Comment System Plugin for WordPress & Ajax Comments - Comment Press the fix is 2.7.2: builds < 2.7.2 are affected, anything from 2.7.2 onward is not.
Remediation
Update to version 2.7.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Comment System Plugin for WordPress & Ajax Comments - Comment Press: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Comment System Plugin for WordPress & Ajax Comments - Comment Press 2.7.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C