dbcve.org
Piotnet FormsWordPress extension · Piotnet

CVE-2023-6220

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-11
Fix available
A fix is available. Upgrade to after 1.0.26 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
The Piotnet Forms plugin for WordPress is vulnerable to arbitrary file uploads due to insufficient file type validation in the 'piotnetforms_ajax_form_builder' function in versions up to, and including, 1.0.28. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 Piotnet Forms WordPress plugin versions up to 1.0.28 contain an arbitrary file upload vulnerability in the piotnetforms_ajax_form_builder function. Due to insufficient file type validation, unauthenticated attackers can upload arbitrary files to the server, potentially achieving remote code execution.

MitigationUpdate the Piotnet Forms plugin to version 1.0.29 or later which contains the proper file type validation fix. Until patched, consider disabling the plugin or deploying WAF rules to block suspicious file upload requests.

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
Piotnet FormsWordPress extension
Affected:<= 1.0.26

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. Confirm Piotnet Forms plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and look for 'Piotnet Forms' in the list. Alternatively, check the filesystem at wp-content/plugins/ for a folder named 'piotnetforms' or similar.
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Identify the installed plugin version
    In WordPress admin, find the Piotnet Forms entry in Plugins list and read the version number displayed beneath the plugin name. Or check the main plugin PHP file for a 'Version:' comment header.
    Affected if The version number is 1.0.26 or lower
  3. Verify the ajax file upload endpoint is accessible
    Check if the file upload functionality exists by examining the plugin files for 'piotnetforms_ajax_form_builder' function or testing access to /wp-admin/admin-ajax.php?action=piotnetforms_ajax_form_builder with a simple request.
    Affected if The ajax handler responds to requests, indicating the vulnerable function is active
  4. Review uploaded files in the uploads directory
    Inspect wp-content/uploads/ and subdirectories for any suspicious file types (php, phtml, exe, js) that were uploaded unexpectedly, particularly from unauthenticated sources.
    Affected if Unexpected executable or script files are found in upload directories that were not intentionally placed there

A user is affected if Piotnet Forms plugin is installed with version 1.0.26 or lower and the file upload ajax functionality is exposed and accessible.

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 1.0.26
Interim mitigation

Update the Piotnet Forms plugin to version 1.0.29 or later which contains the proper file type validation fix. Until patched, consider disabling the plugin or deploying WAF rules to block suspicious file upload requests.

Recommended fix Moderate confidence

Piotnet Forms 1.0.29 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Piotnet Forms' in the plugin list
  4. 4. Check if an update is available for the plugin
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. Verify the update was successful by confirming the new version number (should be higher than 1.0.28)
  7. 7. Test the form functionality to ensure the plugin is working correctly after the update

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

Fix this in Piotnet Forms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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