dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-1056

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Snow Monkey Forms plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the 'generate_user_dirpath' function in all versions up to, and including, 12.0.3. This makes it possible for unauthenticated attackers 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 Snow Monkey Forms WordPress plugin contains an arbitrary file deletion vulnerability in the generate_user_dirpath function due to insufficient file path validation, allowing unauthenticated attackers to delete any file on the server by manipulating path inputs.

MitigationUpdate to version 12.0.4 or later which patches the path validation vulnerability; alternatively, remove the plugin until an update is available.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify Snow Monkey Forms plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or use WP-CLI: wp plugin list --name=snow-monkey-forms
    Affected if The plugin is not installed on the WordPress site
  2. Check installed plugin version
    In WordPress admin, find Snow Monkey Forms in the plugins list and read the version number displayed; alternatively, check the plugin main file header at wp-content/plugins/snow-monkey-forms/snow-monkey-forms.php for the Version tag
    Affected if Version is lower than 12.0.4 (e.g., 12.0.3, 12.0.2, etc.)
  3. Confirm vulnerable function exists in plugin code
    Search the plugin directory (wp-content/plugins/snow-monkey-forms/) for the function named generate_user_dirpath using grep or by opening the relevant PHP file
    Affected if The function exists and contains path traversal logic without proper validation (any version prior to 12.0.4)
  4. Check if the plugin is publicly accessible
    Verify the WordPress site is live and the plugin endpoints are reachable without authentication (the vulnerability is exploitable by unauthenticated users)
    Affected if The site is live and the plugin handles form submissions publicly

You are affected if Snow Monkey Forms plugin is installed with a version lower than 12.0.4 and the site is accessible to unauthenticated users, as the arbitrary file deletion vulnerability can be exploited via directory traversal in the generate_user_dirpath function.

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 12.0.4 or later which patches the path validation vulnerability; alternatively, remove the plugin until an update is available.

Recommended fix Moderate confidence

Snow Monkey Forms version 12.0.4 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Snow Monkey Forms plugin
  4. If an update is available, click 'Update Now' to update to the latest fixed version
  5. Alternatively, download the latest version from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin
  6. Verify the updated version is 12.0.4 or higher after updating

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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