CVE-2023-3452
Canto ≤ 3.0.4
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2023-3452 is a critical-severity PHP Remote File Inclusion (CWE-98) vulnerability in Canto Canto. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The Canto plugin for WordPress is vulnerable to remote file inclusion in versions up to and including 3.0.4. The flaw exists in the handling of the wp_abspath parameter within the tree.php component and is tracked as CWE-98. When the PHP allow_url_include directive is enabled on the server, the issue permits inclusion of arbitrary remote files; local file inclusion is also possible if an attacker can place a malicious file via FTP or another upload path readable by the web server. The vulnerability received a CVSS 3.1 score of 9.8.
Unauthenticated attackers can exploit the weakness over the network without any user interaction or credentials. Successful exploitation grants the ability to execute arbitrary PHP code on the affected WordPress server, resulting in full confidentiality, integrity, and availability impact on the host.
Public references include the vulnerable code in the plugin repository and a subsequent changeset (2951888) that modifies tree.php, indicating an official patch has been issued. The current EPSS score of 0.8711, with a recorded peak of 0.8783, reflects sustained exploitation interest following disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-44114
Vulnerability Data
The Canto plugin for WordPress is vulnerable to Remote File Inclusion in versions up to, and including, 3.0.4 via the 'wp_abspath' parameter. This allows unauthenticated attackers to include and execute arbitrary remote code on the server, provided that allow_url_include is…
more
enabled. Local File Inclusion is also possible, albeit less useful because it requires that the attacker be able to upload a malicious php file via FTP or some other means into a directory readable by the web server.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices such as input validation and allow-listing of include paths directly prevent the weakness.
Hardened runtime configuration (e.g., allow_url_include=off) directly blocks RFI even if code is flawed.
Execution restrictions can prevent the remote payload from running, while eliminating the weakness reduces the need for such controls.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect RFI but does not prevent the weakness by itself.
Secure development lifecycle mandates input validation and safe include/require patterns that directly prevent remote file inclusion.
Application security requirements explicitly call for controls against injection and unsafe file operations.
Secure architecture principles reduce attack surface but do not specifically address dynamic file inclusion.
Secure coding standards directly require whitelisting and sanitization of filenames used in include/require statements.
Information access restriction limits what files can be read but does not address dynamic inclusion logic.