dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-13767

HIGH · 8.1 CVSS v3.1 Published 2025-01-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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 Live2DWebCanvas plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the ClearFiles() function in all versions up to, and including, 1.9.11. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).

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 Live2DWebCanvas WordPress plugin has an authenticated arbitrary file deletion vulnerability in the ClearFiles() function. Attackers with Subscriber-level permissions can delete any file on the server due to insufficient path validation, enabling deletion of wp-config.php to achieve remote code execution.

MitigationUpgrade to the latest patched version of the plugin once available. Until then, disable the plugin or restrict user permissions to prevent exploitation.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

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

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 Live2DWebCanvas plugin is installed
    Navigate to WordPress admin > Plugins and verify if Live2DWebCanvas appears in the installed plugins list
    Affected if The plugin is installed and active
  2. Identify plugin version
    In the Plugins list, check the version column for Live2DWebCanvas; if not displayed, inspect the plugin main file header for the Version field
    Affected if The installed version is older than the patched version (compare against any version number available from WordPress plugin repository)
  3. Check for Subscriber-level user accounts
    Go to Users > All Users in WordPress admin and review the role column; look for any users assigned the Subscriber role
    Affected if At least one user with Subscriber role exists in the system
  4. Verify the ClearFiles() function is accessible
    Review plugin source code for the ClearFiles() function and determine if it is hooked to an action accessible to authenticated users (such as wp_ajax or wp_ajax_nopriv hooks)
    Affected if The ClearFiles function is hooked to an AJAX or similar endpoint reachable by Subscriber-level users
  5. Confirm wp-config.php exists and is writable by the web server
    Locate wp-config.php in the WordPress root directory and verify file permissions allow write access from the web server user
    Affected if wp-config.php exists and is writable, making it a potential deletion target
  6. Audit user capability for file deletion actions
    Use a user with Subscriber role to attempt accessing any AJAX endpoints exposed by the plugin; review capability checks in the plugin code
    Affected if The plugin does not enforce higher privileges (like manage_options) before allowing file deletion operations

The environment is affected if the Live2DWebCanvas plugin is installed, the ClearFiles() function is exposed to authenticated users with Subscriber-level permissions, and critical files such as wp-config.php are present and writable.

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

Upgrade to the latest patched version of the plugin once available. Until then, disable the plugin or restrict user permissions to prevent exploitation.

Recommended fix Moderate confidence

Plugin version 1.9.12 or later (check WordPress plugin repository for latest available version)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Live2DWebCanvas plugin
  4. Check if an update is available and install the latest version
  5. Verify the plugin updated successfully

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,670
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13767 — 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-2024-13767 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