Plugins · dofollow-case-by-case · data as of 2026-11-04
Is DoFollow Case by Case safe? Known vulnerabilities and latest version
- Latest version
- 3.6.1
- Last updated
- 2026-09-30
- Active installs
- 1,000+
- Known issues on record
- 5
- Unpatched in latest
- 0
- Tested up to WP
- 6.9.11
DoFollow Case by Case allows you to selectively apply dofollow to comments and make links in pages or posts nofollow. — by apasionados
What to do
- Update to the latest version (3.6.1). Anything older than 3.6.1 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get dofollow-case-by-case --field=version shows what you run; wp plugin update dofollow-case-by-case updates it.
Check your version
Known vulnerabilities
5 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
high 7.2 CVE-2026-95817 · published 2026-10-02
Stored cross-site scripting (XSS) in DoFollow Case by Case (3.6.0 and older)
- Affected
- 3.6.0 and older
- Fixed in
- 3.6.1 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The DoFollow Case by Case plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content in all versions up to, and including, 3.6.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Comment moderation delays but does not prevent exploitation — once an administrator approves the visually innocuous comment, the stored payload executes in the browser of every subsequent visitor to the affected post.
NVD CVE-2026-95817Wordfence advisoryCode change (fix)Plugin source
medium 4.3 CVE-2025-62102 · published 2025-12-09
Cross-site request forgery (CSRF) in DoFollow Case by Case (3.5.1 and older)
- Affected
- 3.5.1 and older
- Fixed in
- 3.6.0
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Cross-Site Request Forgery (CSRF) vulnerability in apasionados DoFollow Case by Case dofollow-case-by-case allows Cross Site Request Forgery.This issue affects DoFollow Case by Case: from n/a through <= 3.5.1.
high 8.8 CVE-2025-47624 · published 2025-05-07
Cross-site request forgery (CSRF) in DoFollow Case by Case (3.5.1 and older)
- Affected
- 3.5.1 and older
- Fixed in
- 3.6.0
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Cross-Site Request Forgery (CSRF) vulnerability in apasionados DoFollow Case by Case dofollow-case-by-case allows Cross Site Request Forgery.This issue affects DoFollow Case by Case: from n/a through <= 3.5.1.
medium 4.8 CVE-2025-47625 · published 2025-05-07
Stored cross-site scripting (XSS) in DoFollow Case by Case (3.5.1 and older)
- Affected
- 3.5.1 and older
- Fixed in
- 3.6.0
- Access needed (per CVSS)
- Needs an admin-level account; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in apasionados DoFollow Case by Case dofollow-case-by-case allows Stored XSS.This issue affects DoFollow Case by Case: from n/a through <= 3.5.1.
high 8.8 CVE-2023-49197 · published 2023-12-15
Cross-site request forgery (CSRF) in DoFollow Case by Case (3.4.2 and older)
- Affected
- 3.4.2 and older
- Fixed in
- 3.5.0
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Cross-Site Request Forgery (CSRF) vulnerability in Apasionados, Apasionados del Marketing, NetConsulting DoFollow Case by Case.This issue affects DoFollow Case by Case: from n/a through 3.4.2.
Recent activity
- 2026-09-30 — latest release on wordpress.org (3.6.1).
- 2026-10-02 — Stored cross-site scripting (XSS) disclosed (CVE-2026-95817), fixed in 3.6.1.
- 2025-12-09 — Cross-site request forgery (CSRF) disclosed (CVE-2025-62102), fixed in 3.6.0.
- 2025-05-07 — Cross-site request forgery (CSRF) disclosed (CVE-2025-47624), fixed in 3.6.0.
Get an email when DoFollow Case by Case has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for DoFollow Case by Case (dofollow-case-by-case) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Cross-site request forgery (CSRF) (3) · Cross-site scripting (XSS) (2)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/dofollow-case-by-case (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/dofollow-case-by-case"><img src="https://laskyr.com/plugins/dofollow-case-by-case/badge.svg" alt="DoFollow Case by Case vulnerability status"></a>