# CVE-2023-3452: Canto <= 3.0.4 - Unauthenticated Remote File Inclusion

> Unauthenticated attackers can execute arbitrary remote code on the server via Remote File Inclusion if allow_url_include is enabled.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-r7j9-2qv5-fpm9

## What is CVE-2023-3452?

CVE-2023-3452 is a critical code injection vulnerability in flightbycanto Canto, published on 12 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 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.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

## Which versions are affected by CVE-2023-3452?

It affects 1 product.


Products: Canto Canto.

## How do I fix CVE-2023-3452?

No fix has been published for CVE-2023-3452 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-3452 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3452 exists.

Public exploit code:

- Wordpress Plugin Canto < 3.0.5 - Remote File Inclusion (RFI) and Remote Code Execution (RCE) (github_poc): https://github.com/leoanggal1/CVE-2023-3452-PoC
- CVE-2023-3452 exploit for WordPress Canto plugin RCE, HTTPS support included (github_poc): https://github.com/Alpastx/CVE-2023-3452---WordPress-Canto-Plugin-RCE
-  this is a metasploit exploit module for CVE-2024-25096 and CVE-2023-3452  (github_poc): https://github.com/puppetma4ster/Metasploit-Wordpress-Canto-Exploit-RCE
- WordPress Canto Plugin <= 3.0.4 - File Inclusion (nuclei): http/cves/2023/CVE-2023-3452.yaml

## Other vulnerabilities in flightbycanto Canto

- [CVE-2024-25096](https://insights.sbomify.com/CVE-2024-25096/): WordPress canto plugin <= 3.0.7 - Unauth. Remote Code Execution (RCE) vulnerability (critical 10.0)
- [CVE-2024-4936](https://insights.sbomify.com/CVE-2024-4936/): Canto <= 3.0.8 - Unauthenticated Remote File Inclusion (critical 9.8)
- [CVE-2022-40305](https://insights.sbomify.com/CVE-2022-40305/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2020-24063](https://insights.sbomify.com/CVE-2020-24063/): Server-side request forgery in n/a (high 7.2)
- [CVE-2020-28976](https://insights.sbomify.com/CVE-2020-28976/): Server-side request forgery in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3452 and fix it if it is affected.

What it is: CVE-2023-3452 is a critical code injection vulnerability in flightbycanto Canto, published on 12 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3452 exists.

Affected product: flightbycanto Canto. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-3452/ (Markdown: https://insights.sbomify.com/CVE-2023-3452/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-3452
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-3452
- OSV: https://osv.dev/vulnerability/CVE-2023-3452

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-3452/
Summaries are generated and may contain mistakes; the official description above is the record.