
Canto Security & Risk Analysis
wordpress.org/plugins/cantoFind & publish creative assets to WordPress easily, no email or folder search needed, with Canto's digital asset management.
Is Canto Safe to Use in 2026?
Generally Safe
Score 89/100Canto has a strong security track record. Known vulnerabilities have been patched promptly.
The 'canto' plugin version 3.1.1 exhibits a mixed security posture. While it shows strengths in its handling of SQL queries and output escaping, with 100% of SQL queries using prepared statements and 90% of outputs properly escaped, significant concerns are raised by the attack surface and its vulnerability history. The static analysis reveals a substantial attack surface with 4 AJAX handlers, all of which lack authentication checks. This is a major security flaw, as it exposes these endpoints to unauthorized access and potential exploitation.
The plugin's vulnerability history is alarming, with 7 known CVEs, including 3 critical and 4 high-severity issues. The prevalence of 'PHP Remote File Inclusion' and 'Server-Side Request Forgery' vulnerabilities in its past suggests recurring weaknesses in how the plugin handles user input, file operations, and external requests. The fact that the last vulnerability was reported very recently (2024-06-13) indicates ongoing security challenges.
In conclusion, while the plugin has some good practices in place, the unprotected AJAX endpoints and the extensive history of critical and high-severity vulnerabilities, particularly those related to file inclusion and SSRF, present a significant risk. These weaknesses outweigh the positive aspects of its code, making it a potentially dangerous component if not thoroughly secured or updated.
Key Concerns
- 4 AJAX handlers without auth checks
- Total 7 known CVEs (3 critical, 4 high)
- Flows with unsanitized paths
- Vulnerability history includes RFI and SSRF
- Lack of capability checks
- Only 1 nonce check
Canto Security Vulnerabilities
CVEs by Year
Severity Breakdown
7 total CVEs
Canto <= 3.0.8 - Unauthenticated Remote File Inclusion
Canto <= 3.0.6 - Remote File Inclusion to Code Execution
Canto <= 3.0.4 - Unauthenticated Remote File Inclusion
Canto <= 1.9.0 - Blind Server-Side Request Forgery via detail.php
Canto <= 1.9.0 - Blind Server-Side Request Forgery via download.php
Canto <= 1.9.0 - Blind Server-Side Request Forgery via get.php
Canto <= 1.9.0 - Blind Server-Side Request Forgery via tree.php
Canto Code Analysis
Output Escaping
Data Flow Analysis
Canto Attack Surface
AJAX Handlers 4
WordPress Hooks 20
Scheduled Events 1
Maintenance & Trust
Canto Maintenance & Trust
Maintenance Signals
Community Trust
Canto Alternatives
pixx.io
pixx-io
Integrate pixx.io DAM Digital Asset Management into WordPress. Use files from your pixx.io media pool with WordPress easily and without any detour.
OpenAsset
openasset
Sync your AEC Project Portfolio, Employees and Images from OpenAsset to your Wordpress Website.
Pics.io digital asset management for WordPress
pics-io
Insert images from your Pics.io Digital asset management to a post without leaving WP admin.
HIVO Connector
hivo-library
Login to your HIVO Library and add Assets directly to your Wordpress Media tab.
Vy Bildbank
vy-bildbank
Access your media assets from your account at the cloud service Vy Bildbank.
Canto Developer Profile
1 plugin · 100 total installs
How We Detect Canto
Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.
Asset Fingerprints
/wp-content/plugins/canto/block/block.js/wp-content/plugins/canto/block/block.jsHTML / DOM Fingerprints
acf-fields-containeracf-field-imageacf-field-labelacf-imagedata-post-iddata-canto-acfdata-field-namedata-field-typecanto_acf_fields_loaded/wp-json/wp/v2/posts?_fields[]=canto_acf_fields