Is canto (WordPress plugin) vulnerable?

WordPress canto has 6 known advisories in the phpwarden feed. Feed 2026.10.29.3, updated 2026-10-29.

6advisories
2critical
0on CISA KEV
5no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2020-28976The Canto plugin 1.3.0 for WordPress contains a blind SSRF vulnerability. It allows an unauthenticated attacker can make a request to any inmedium5.3=1.3.0–
CVE-2020-28977The Canto plugin 1.3.0 for WordPress contains blind SSRF vulnerability. It allows an unauthenticated attacker can make a request to any intemedium5.3=1.3.0–
CVE-2020-28978The Canto plugin 1.3.0 for WordPress contains blind SSRF vulnerability. It allows an unauthenticated attacker can make a request to any intemedium5.3=1.3.0–
CVE-2023-3452The Canto plugin for WordPress is vulnerable to Remote File Inclusion in versions up to, and including, 3.0.4 via the 'wp_abspath' parametercritical9.8<=3.0.4–
CVE-2020-24063The Canto plugin 1.3.0 for WordPress allows includes/lib/download.php?subdomain= SSRF.high7.2=1.3.0–
CVE-2024-4936The Canto plugin for WordPress is vulnerable to Remote File Inclusion in all versions up to, and including, 3.0.8 via the abspath parameter.critical9.8<3.0.93.0.9

Am I affected?

Find out in one command. phpwarden checks your WordPress install against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden wordpress /var/www/html

# or, without Composer
pipx install phpwarden   &&   phpwarden wordpress /var/www/html

Or keep it checked automatically with the GitHub Action or a nightly cron; see WordPress docs.

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.