dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-52705

CRITICAL · 9.0 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/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
Unauthenticated Arbitrary File Upload in SigmaForms Pro – AI Generated Forms <= 1.4.5 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 · high confidence

An unauthenticated arbitrary file upload vulnerability in SigmaForms Pro – AI Generated Forms plugin versions 1.4.5 and below allows remote attackers to upload malicious files directly to the server without any authentication credentials, potentially leading to remote code execution.

MitigationUpdate SigmaForms Pro to the latest version immediately. If no patched version is available, disable the plugin, implement WAF rules to block unauthorized file upload endpoints, and remove any uploaded files from writable directories.

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

CVSS:3.1/AV:N/AC:H/PR:N/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. Confirm SigmaForms Pro plugin is installed
    Access your WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'SigmaForms Pro - AI Generated Forms' in the list of active plugins.
    Affected if The plugin appears in the installed plugins list, indicating the product is in use.
  2. Identify the installed version number
    In the Plugins list, click on the plugin to view its details, or check the plugin header file for the version string. Alternatively, examine the plugin's main PHP file for a 'Version:' comment or $version variable.
    Affected if The version number is 1.4.5 or lower, placing it within the affected range.
  3. Verify file upload functionality is enabled
    Check the plugin settings page for any file upload or form builder features. Look for any enabled options that allow file attachments or form submissions with file inputs.
    Affected if File upload features are active or form builder includes upload-capable form elements.
  4. Test if upload endpoint accepts unauthenticated requests
    Send a POST request to common plugin upload endpoints (such as /wp-admin/admin-ajax.php with action=sigmaForms or similar) without including authentication cookies or credentials. Observe if the server accepts the request.
    Affected if The endpoint accepts and processes file upload requests without requiring authentication tokens.
  5. Inspect upload directories for suspicious files
    Examine the wp-content/uploads directory and any plugin-specific upload folders. Look for unexpected file types such as .php, .phtml, .phar, or other executable extensions that were not intentionally uploaded.
    Affected if Unexpected script files or executable content exists in upload directories, indicating potential exploitation.

A user is affected if the SigmaForms Pro plugin version is 1.4.5 or below AND file upload functionality is enabled, allowing unauthenticated attackers to potentially upload malicious executable files.

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 SigmaForms Pro to the latest version immediately. If no patched version is available, disable the plugin, implement WAF rules to block unauthorized file upload endpoints, and remove any uploaded files from writable directories.

Recommended fix Moderate confidence

Version higher than 1.4.5 (contact vendor for exact fixed release)

  1. 1. If possible, disable the SigmaForms Pro plugin temporarily to prevent exploitation until a fix is applied.
  2. 2. Contact SigmaForms support or check their official release channels for the fixed version.
  3. 3. After the vendor releases a security update, upgrade to the latest version of SigmaForms Pro immediately.
  4. 4. Audit the web server for any suspicious files that may have been uploaded via this vulnerability.
  5. 5. Review user accounts and server logs for any unauthorized access or changes.

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

Have this fixed 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 help mitigating

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-2026-52705 — 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-52705 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