Erident Custom Login & Dashboard <= 3.4.1 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 3.5
- Affected Plugin
- Erident Custom Login and Dashboard
- Affected Version
<= 3.4.1- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE pending
At a glance
This record tracks a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Erident Custom Login and Dashboard WordPress plugin, affecting versions <= 3.4.1. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.5; sites on affected versions should update now. Disclosed June 2015.
Vulnerability Overview
The Erident Custom Login & Dashboard plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.4.1. This is due to missing or incorrect nonce validation in the 'erident-custom-login-and-dashboard/trunk/er-custom-login.php' file. This makes it possible for unauthenticated attackers to modify the plugin's settings via a 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 confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Erident Custom Login and Dashboard <= 3.4.1 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 Erident Custom Login and Dashboard the fix is 3.5: builds <= 3.4.1 are affected, anything from 3.5 onward is not.
Remediation
Update to version 3.5, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Erident Custom Login and Dashboard: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Erident Custom Login and Dashboard 3.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Erident Custom Login and Dashboard
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C