Skip to main content
VulnerabilityPublished

CVE-2026-92895: Live2DWebCanvas (WordPress plugin) · Unrestricted File Upload

Affects Live2DWebCanvas (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High.

Data as of 6 Nov 2026, 11:41 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.18.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
jiangweifangLive2DWebCanvasAffected
  • <=2.2.1
Fixed in–

AI-suggested

Users should avoid enabling the custom-local apiType setting, which is required for remote code execution exploitation. Monitor vendor advisories for updates or patches addressing this vulnerability. Until a fix is available, restrict access to the plugin directory and consider disabling or removing the Live2DWebCanvas plugin if the custom-local mode is in use.

Description

The Live2DWebCanvas WordPress plugin up to version 2.2.1 contains an arbitrary file upload vulnerability due to lack of file extension and MIME type validation in the download_one_file function. This allows unauthenticated attackers to upload potentially executable files to the web-accessible plugin directory. Remote code execution is possible if the plugin is configured with the non-default custom-local apiType setting, which requires a paid license and exposes REST nonce and session tokens on front-end pages.

References

Community reviews

Loading reviews…