dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-3335

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Canto plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 3.1.1 via the `/wp-content/plugins/canto/includes/lib/copy-media.php` file. This is due to the file being directly accessible without any authentication, authorization, or nonce checks, and the `fbc_flight_domain` and `fbc_app_api` URL components being accepted as user-supplied POST parameters rather than read from admin-configured options. Since the attacker controls both the destination server and the `fbc_app_token` value, the entire fetch-and-upload chain is attacker-controlled — the server never contacts Canto's legitimate API, and the uploaded file originates entirely from the attacker's infrastructure. This makes it possible for unauthenticated attackers to upload arbitrary files (constrained to WordPress-allowed MIME types) to the WordPress uploads directory. Additional endpoints (`detail.php`, `download.php`, `get.php`, `tree.php`) are also directly accessible without authentication and make requests using a user-supplied `app_api` parameter combined with an admin-configured subdomain.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Canto WordPress plugin has a Missing Authorization vulnerability in multiple PHP files (copy-media.php, detail.php, download.php, get.php, tree.php) that are directly accessible without authentication. The copy-media.php file accepts user-supplied POST parameters for the destination server and API token rather than using admin-configured options, allowing unauthenticated attackers to upload arbitrary files (constrained to WordPress-allowed MIME types) to the uploads directory.

MitigationImmediately restrict access to the affected PHP files by adding authentication/authorization checks, and refactor the code to use admin-configured options instead of user-supplied POST parameters for fbc_flight_domain, fbc_app_api, and fbc_app_token.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Canto plugin installation
    Check the WordPress plugin directory for the Canto plugin folder (typically /wp-content/plugins/canto/) and identify the installed version from the plugin header or version file
    Affected if The Canto plugin is installed and the version matches or falls within the affected range (verify against official plugin changelog for when the authorization checks were added)
  2. Identify vulnerable PHP files
    Check for the presence of the following files in the Canto plugin directory: copy-media.php, detail.php, download.php, get.php, and tree.php. These are typically located in the plugin's inc/ or includes/ subdirectory
    Affected if Any of these files exist in the plugin directory, indicating they may be directly accessible
  3. Verify unauthenticated access is possible
    Attempt to access one of the vulnerable PHP files directly via HTTP request (e.g., GET or POST to the file's URL without any authentication cookies/tokens) or inspect server configuration to confirm these files respond to unauthenticated requests
    Affected if The files respond to requests without requiring WordPress authentication (logged-in status check)
  4. Check copy-media.php parameter handling
    Inspect the copy-media.php file source code to determine if it accepts and uses POST parameters (fbc_flight_domain, fbc_app_api, fbc_app_token) from user input rather than reading from admin-configured plugin options
    Affected if The code processes user-supplied POST parameters for destination server, API token, or similar sensitive configuration instead of using admin-saved options stored in wp_options
  5. Review plugin configuration storage
    Examine the WordPress database wp_options table for Canto plugin settings. Check if the plugin stores fbc_app_token, fbc_flight_domain, and related configuration values as admin-saved options rather than requiring them per-request
    Affected if The plugin does not store the required credentials/parameters in wp_options and instead expects them to be passed with each upload request

A user is affected if the Canto WordPress plugin is installed, the vulnerable PHP files (copy-media.php, detail.php, download.php, get.php, tree.php) exist and are accessible without authentication, and copy-media.php uses user-supplied POST parameters instead of admin-configured options for sensitive settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately restrict access to the affected PHP files by adding authentication/authorization checks, and refactor the code to use admin-configured options instead of user-supplied POST parameters for fbc_flight_domain, fbc_app_api, and fbc_app_token.

Recommended fix Moderate confidence

Canto plugin version 3.1.2 or later (verify current latest version at wordpress.org/plugins/canto)

  1. Check the WordPress plugin repository for the Canto plugin to identify the current version
  2. If version 3.1.2 or higher is available, update the plugin through WordPress admin dashboard under Plugins > All Plugins > Canto > Update Now
  3. If no update is available from the WordPress plugin repository, consider temporarily disabling the Canto plugin until a patched version is released
  4. Alternatively, contact the plugin vendor directly to request a patched version that addresses the missing authorization vulnerability in copy-media.php and related endpoint files
Caveat Review plugin changelog for any breaking changes between 3.1.1 and the new version before updating

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3335 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3335 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data