dbcve.org
Piotnet FormsWordPress extension · Piotnet

CVE-2023-51412

CRITICAL · 9.8 CVSS v3.1 Published 2023-12-29
Fix available
A fix is available. Upgrade to after 1.0.25 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
Unrestricted Upload of File with Dangerous Type vulnerability in Piotnet Piotnet Forms.This issue affects Piotnet Forms: from n/a through 1.0.25.

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 · moderate confidence

Unrestricted file upload vulnerability in Piotnet Forms allows attackers to upload dangerous file types (e.g., executable scripts) without proper validation. This can lead to remote code execution if the uploaded files are accessible via the web server.

MitigationImplement strict allowlist-based file type validation including extension checking, MIME type verification, and magic byte validation. Store uploads outside the webroot or disable script execution in the upload directory.

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.25

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. Locate Piotnet Forms plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for the 'piotnet-forms' folder, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' or similar plugin inventory query
    Affected if The plugin folder 'piotnet-forms' exists in the plugins directory or is listed in active plugins
  2. Determine installed version
    Read the main plugin file header in wp-content/plugins/piotnet-forms/piotnet-forms.php and look for 'Version:' field, or query the WordPress options table: SELECT option_value FROM wp_options WHERE option_name LIKE '%piotnet_forms%version%'
    Affected if The reported version is 1.0.25 or lower
  3. Identify if forms with file upload exist
    Check WordPress database for form definitions containing upload fields: SELECT * FROM wp_posts WHERE post_type = 'piotnet-forms' AND post_content LIKE '%file%upload%' or inspect published forms for file input fields
    Affected if Any Piotnet Forms with file upload fields are created and published on the site
  4. Verify upload directory is web-accessible
    Check the wp-content/uploads/ directory structure and verify .htaccess or nginx config does not block script execution in upload folders; inspect if uploads are stored inside the webroot rather than outside it
    Affected if Upload directory is web-accessible and script execution is not explicitly disabled (no restrictions on .php, .exe, .js file types)

The environment is affected if Piotnet Forms version 1.0.25 or lower is installed, forms with file upload functionality exist, and uploads are stored in a web-accessible directory without script execution restrictions.

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.25
Interim mitigation

Implement strict allowlist-based file type validation including extension checking, MIME type verification, and magic byte validation. Store uploads outside the webroot or disable script execution in the upload directory.

Recommended fix Moderate confidence

Piotnet Forms 1.0.26 or latest available version

  1. 1. Back up your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Locate Piotnet Forms in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Verify the update was successful by checking the plugin version after updating
  6. 6. Test file upload functionality to ensure the plugin continues to work 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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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