DoFollow Case by Case
dofollow-case-by-case · plugin
Known security vulnerabilities for DoFollow Case by Case. Find out in seconds which version runs on your site with WP Lens.
5 known vulnerabilities
4 exploitable without logging in · latest Oct 2, 2026
Listed on wordpress.org · latest 3.6.1 · last updated Sep 30, 2026 · 1K+ installs
wordpress.org status checked on Oct 5, 2026
Vulnerabilities
- High 8.8
CVE-2025-47624unauthenticated · needs a click≤ 3.5.1
WordPress DoFollow Case by Case plugin <= 3.5.1 - Cross Site Request Forgery (CSRF) vulnerability
- High 8.8
CVE-2023-49197unauthenticated · needs a click≤ 3.4.2
WordPress DoFollow Case by Case Plugin <= 3.4.2 is vulnerable to Cross Site Request Forgery (CSRF)
- High 7.2
CVE-2026-95817unauthenticated≤ 3.6.0
DoFollow Case by Case <= 3.6.0 - Unauthenticated Stored Cross-Site Scripting via Comment Content
- Medium 4.8
CVE-2025-47625high privilege≤ 3.5.1
WordPress DoFollow Case by Case plugin <= 3.5.1 - Cross Site Scripting (XSS) vulnerability
- Medium 4.3
CVE-2025-62102unauthenticated · needs a click≤ 3.5.1
WordPress DoFollow Case by Case plugin <= 3.5.1 - Cross Site Request Forgery (CSRF) vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).