CVE-2026-92895 · Package
NO FIX YET · SEE WHAT TO DO
The Live2DWebCanvas WordPress plugin up to and including 2.2.1 writes files from attacker-controlled manifest entries into its web-served directory without extension or MIME checks. An unauthenticated attacker can upload executable files, which may allow remote code execution when the non-default custom-local apiType mode is enabled.
first public Nov 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the Live2DWebCanvas WordPress plugin at version 2.2.1 or earlier are exposed. The code-execution path needs the non-default custom-local apiType setting, which requires a paid license; sites without that setting enabled are less exposed, but the upload flaw itself is reachable without an account. Sites that do not run this plugin can skip it.
Not affected if apitype-not-custom-local, plugin-above-2.2.1, plugin-not-installed
Who cares self-hosted, wordpress, wordpress-plugin
2.2.1 or earlier is affected.2.2.1; the fixed version is not named in the sources.The Live2DWebCanvas plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 2.2.1 via the download_one_file function. This is due to missing file extension whitelist and MIME type validation in download_one_file() when writing files derived from attacker-controlled manifest entries to the web-served plugin directory. This makes it possible for unauthenticated attackers to upload files that may be executable, which makes remote code execution possible when the plugin's apiType setting is configured as custom-local (self-hosted model mode), a non-default option that requires a paid license and prints the REST nonce and one-time session tokens into every front-end page.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.