dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-2932

HIGH · 8.8 CVSS v3.1 Published 2025-07-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 JKDEVKIT plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the 'font_upload_handler' function in all versions up to, and including, 1.9.4. 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). If WooCommerce is enabled, attackers will need Contributor-level access and above.

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 JKDEVKIT WordPress plugin fails to validate file paths in its font_upload_handler function, allowing authenticated attackers with Subscriber-level access (or Contributor with WooCommerce) to manipulate file paths and delete arbitrary files on the server. Deleting critical files like wp-config.php enables remote code execution.

MitigationUpdate to version 1.9.5 or later to patch the vulnerability. If immediate patching is not feasible, disable the JKDEVKIT plugin until a patch can be applied.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 JKDEVKIT plugin is installed
    Check the WordPress plugins directory at wp-content/plugins/ for a folder named jkdevkit, or look for JKDEVKIT in the WordPress admin under Plugins > Installed Plugins
    Affected if The plugin folder jkdevkit exists in wp-content/plugins/ or the plugin appears in the WordPress plugins list
  2. Identify the installed JKDEVKIT version
    Open the main plugin file (typically wp-content/plugins/jkdevkit/jkdevkit.php) and look for the version header comment at the top of the file, or check the version column in Plugins > Installed Plugins
    Affected if The version is 1.9.4 or lower (or if no version is displayed and the plugin has not been updated recently)
  3. Verify WordPress user registration is open
    In WordPress admin, go to Settings > General and check 'Membership: Anyone can register' - if enabled, any visitor can register with a selected default role
    Affected if Anyone can register is enabled and the default role is set to Subscriber or Contributor
  4. Audit existing user accounts with Subscriber or Contributor roles
    In WordPress admin, go to Users and filter or examine the list for accounts with Subscriber or Contributor roles, especially accounts you do not recognize
    Affected if There are Subscriber or Contributor accounts that were not created by known administrators, particularly accounts created recently
  5. Check for evidence of file deletion attempts
    Review web server access logs and error logs for requests to /wp-admin/admin-ajax.php with action=jkdevkit_font_upload or similar font_upload_handler calls, and check for suspicious path traversal patterns like ../ in parameters
    Affected if AJAX requests to the plugin contain path traversal sequences or critical files such as wp-config.php have been recently modified or deleted

You are affected if the JKDEVKIT plugin version is 1.9.4 or lower AND either user registration is open to Subscribers/Contributors OR unknown Subscriber/Contributor accounts exist on your site

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

Update to version 1.9.5 or later to patch the vulnerability. If immediate patching is not feasible, disable the JKDEVKIT plugin until a patch can be applied.

Recommended fix Moderate confidence

Latest version after 1.9.4 (verify current fixed release in WordPress plugin repository)

  1. 1. Update the JKDEVKIT plugin to the latest available version from the WordPress plugin repository
  2. 2. If automatic updates are not enabled, manually upload the latest version through Plugins > Add New > Upload Plugin
  3. 3. Verify the update was successful by checking the plugin version number
  4. 4. Confirm that the font_upload_handler function is no longer accessible to Subscriber-level users
  5. 5. If possible, review server logs for any suspicious file deletion attempts targeting wp-config.php or other critical files

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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