dbcve.org
Snow Monkey FormsWordPress extension · Snow Monkey Forms Project

CVE-2023-28413

CRITICAL · 9.8 CVSS v3.1 Published 2023-05-23
Fix available
A fix is available. Upgrade to after 5.0.6 or later.
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
Directory traversal vulnerability in Snow Monkey Forms versions v5.0.6 and earlier allows a remote unauthenticated attacker to obtain sensitive information, alter the website, or cause a denial-of-service (DoS) condition.

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

Directory traversal vulnerability in the Snow Monkey Forms WordPress plugin versions 5.0.6 and earlier allows remote unauthenticated attackers to access files outside the web document root via manipulated file path inputs, potentially exposing sensitive server configuration files, credentials, or other confidential data.

MitigationUpdate Snow Monkey Forms to the latest version immediately. If no patched version is available, disable the plugin until a fix is released and audit for any signs of compromise.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Snow Monkey FormsWordPress extension
Affected:<= 5.0.6

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
    Navigate to WordPress admin dashboard > Plugins. Look for 'Snow Monkey Forms' in the installed plugins list.
    Affected if The plugin is installed and appears in the plugins list.
  2. Check installed plugin version
    In WordPress admin > Plugins, find Snow Monkey Forms and view the version number displayed under the plugin name, or check the plugin header in wp-content/plugins/snow-monkey-forms/readme.txt for the 'Version' field.
    Affected if The installed version is 5.0.6 or lower.
  3. Confirm plugin is active
    In WordPress admin > Plugins, check if Snow Monkey Forms shows as 'Active' rather than 'Inactive' or 'Network Active'.
    Affected if The plugin is currently active.
  4. Inspect plugin file structure for vulnerable endpoint
    Check for the existence of form-submission related PHP files in wp-content/plugins/snow-monkey-forms/src directory that handle file path parameters. Look for files that process file path inputs without proper sanitization.
    Affected if The plugin contains file handling code that accepts path parameters.

If Snow Monkey Forms plugin is installed, active, and running version 5.0.6 or earlier, the environment is affected by this directory traversal vulnerability.

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
Upgrade available Upgrade to a release after 5.0.6
Interim mitigation

Update Snow Monkey Forms to the latest version immediately. If no patched version is available, disable the plugin until a fix is released and audit for any signs of compromise.

Recommended fix Moderate confidence

Snow Monkey Forms version 5.0.7 or later

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find Snow Monkey Forms in the plugin list
  5. 5. Click 'Update now' if an update is available, or manually download the latest version from the WordPress plugin repository
  6. 6. Verify the plugin is updated to version 5.0.7 or later
  7. 7. Test that forms functionality works correctly after the update
  8. 8. Monitor the site for any unusual behavior

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

Fix this in Snow Monkey Forms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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