WordPress security by component
DoFollow Case by Case
Plugin description
DoFollow Case by Case is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published Dec 09, 2025; the highest CVE/CNA score is 5.9.
Plugin slug:
dofollow-case-by-caseLatest vulnerability
CVE-2025-62102: DoFollow Case by Case: Cross-site request forgery
DoFollow Case by Case is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
| Safe version |
|
||
|---|---|---|---|
| Dec 09, 2025 |
CVE-2025-62102
DoFollow Case by Case: Cross-site request forgery
DoFollow Case by Case is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE4.3
NVDPending
|
| May 07, 2025 |
CVE-2025-47625
DoFollow Case by Case: Cross-site scripting
DoFollow Case by Case is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE5.9
NVD4.8
|
| May 07, 2025 |
CVE-2025-47624
DoFollow Case by Case: Cross-site request forgery
DoFollow Case by Case is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE4.3
NVD8.8
|
| Dec 15, 2023 |
CVE-2023-49197
DoFollow Case by Case: Cross-site request forgery
DoFollow Case by Case is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE4.3
NVD8.8
|