dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-56058

CRITICAL · 9.9 CVSS v3.1 Published 2026-06-26
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 Zero-click 8 weeks old

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
Subscriber Arbitrary File Upload in Quform <= 2.23.0 versions.

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

The Quform WordPress plugin versions 2.23.0 and below contains an arbitrary file upload vulnerability that allows users with the Subscriber role to upload malicious files to the server. This critical flaw enables attackers to potentially achieve remote code execution by uploading web shells or other executable content.

MitigationUpdate Quform to the latest patched version immediately. Until patched, disable file upload forms or restrict uploads to trusted user roles (Editor/Admin only) via WordPress user role settings.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Check if Quform plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Quform' or check wp-content/plugins/ directory for quform folder. The version is typically displayed on the plugin page.
    Affected if Quform version 2.23.0 or lower is installed
  2. Verify installed Quform version
    In WordPress admin, navigate to Quform > Settings > License, or check the version number displayed on the Plugins page. Compare against 2.23.0.
    Affected if Installed version is 2.23.0 or lower (versions above 2.23.0 are patched)
  3. Identify if any Quform forms have file upload enabled
    In WordPress admin, go to Quform > Forms and review each form. Open form builder and check if a File Upload element is present and enabled.
    Affected if Any active Quform form contains a File Upload element that is accessible to users
  4. Verify if Subscriber role can access file upload forms
    Check WordPress user role permissions. Go to Users > Roles (or use a role management plugin). Verify whether Subscriber role has permission to submit forms that contain file upload fields, or check if forms are set to allow Subscriber access.
    Affected if Subscriber role users can access and submit forms with file upload capability

Environment is affected if Quform version 2.23.0 or lower is installed AND there are forms with file upload elements accessible to Subscriber role users.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Quform to the latest patched version immediately. Until patched, disable file upload forms or restrict uploads to trusted user roles (Editor/Admin only) via WordPress user role settings.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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