PlugNedit Adaptive Editor < 6.2.0 - Cross-Site Request Forgery leading to Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 6.2.0
- Affected Plugin
- plugnedit
- Affected Version
< 6.2.0- CVSS
- 6.5Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2015-9422
At a glance
CVE-2015-9422 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the plugnedit WordPress plugin, affecting versions < 6.2.0. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 6.2.0; sites on affected versions should update now. Disclosed August 2015, reported by Marcin Probola.
Vulnerability Overview
The PlugNedit Adaptive Editor plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions before 6.2.0. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page via forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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. A successful exploit has high impact on integrity.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in plugnedit < 6.2.0 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For plugnedit the fix is 6.2.0: builds < 6.2.0 are affected, anything from 6.2.0 onward is not.
Remediation
Update to version 6.2.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to plugnedit: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: plugnedit 6.2.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in plugnedit
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C