Skip to main content
CVE-2026-92895VulnerabilityPublished

The Live2DWebCanvas plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-92895· High 8.1

Not known to be exploited · CVSS 8.1 High.

Data as of 6 Nov 2026, 13:22 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

Since the vulnerability affects all versions up to and including 2.2.1, users should check the vendor advisory for updates or patches. Until a fix is available, avoid using the custom-local apiType setting, especially in publicly accessible environments, and restrict access to the plugin directory. Monitor vendor channels for official remediation guidance.

Description

The Live2DWebCanvas WordPress plugin versions up to and including 2.2.1 contain an arbitrary file upload vulnerability via the download_one_file function. This flaw arises from missing file extension and MIME type validation, allowing unauthenticated attackers to upload potentially executable files. 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…