DoFollow Case by Case <= 3.4.2 Cross-Site Request Forgery via getEmail and getUrl
Strategic Overview
- Status
- Patched in 3.5.0
- Affected Plugin
- DoFollow Case by Case
- Affected Version
< 3.5.0- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-49197
At a glance
CVE-2023-49197 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the DoFollow Case by Case WordPress plugin, affecting versions < 3.5.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.5.0; sites on affected versions should update now. Disclosed September 2023, reported by Skalucy.
Vulnerability Overview
The DoFollow Case by Case plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.4.2. This is due to missing or incorrect nonce validation on the 'getEmail' and 'getUrl' functions. This makes it possible for unauthenticated attackers to add emails and URLs to the plugin's allowlist 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.
CWE-352: Cross-Site Request Forgery (CSRF)
DoFollow Case by Case < 3.5.0 carries this weakness at getEmail, and reaching it 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 DoFollow Case by Case the fix is 3.5.0: builds < 3.5.0 are affected, anything from 3.5.0 onward is not.
Remediation
Update to version 3.5.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to DoFollow Case by Case: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: DoFollow Case by Case 3.5.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in DoFollow Case by Case
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C