CVE-2026-5192
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 · uneditedThe Forminator Forms – Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Path Traversal in versions up to, and including, 1.52.1 via the 'upload-1[file][file_path]' parameter. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. Successful exploitation requires a publicly accessible form with a File Upload field where Save and Continue is enabled in that form's Behavior settings and the Save and Continue email notification is configured to attach uploaded files in Email Notifications.
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 confidenceThe Forminator plugin for WordPress contains a path traversal vulnerability in the Save and Continue feature's file upload handling. The 'upload-1[file][file_path]' parameter does not properly sanitize input, allowing unauthenticated attackers to read arbitrary files on the server by manipulating file paths (e.g., ../../etc/passwd).
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Forminator plugin is installedNavigate to WordPress admin > Plugins and check if Forminator plugin is active, or check the plugins directory for forminator/ folderAffected if Forminator plugin is present and active
-
Identify installed Forminator versionCheck the plugin version in WordPress admin > Plugins > Forminator, or inspect forminator/readme.txt for the Version field, or query the database wp_options table for the 'forminator_version' optionAffected if Version is below 1.52.2 (vulnerable)
-
Check for forms with File Upload fieldsNavigate to Forminator > Forms and examine each form for a File Upload field type, or query the wp_posts table for posts with post_type='forminator_forms' and content containing 'file-upload'Affected if Any form contains a File Upload field and the Save and Continue feature is in use
-
Verify Save and Continue feature is enabledEdit each form with File Upload fields and check Form Settings > Save and Continue, or inspect form meta data in wp_postmeta for '_forminator_save_and_continue' meta_keyAffected if Save and Continue is enabled on forms with File Upload fields
-
Look for signs of path traversal exploitationReview web server access logs for requests containing 'upload-1[file][file_path]' parameter with '../' sequences, or check application logs for path traversal attemptsAffected if Suspicious path traversal patterns found in logs
A user is affected if Forminator version is below 1.52.2 AND they have forms with File Upload fields that have Save and Continue feature enabled, making the 'upload-1[file][file_path]' parameter exploitable.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to version 1.52.2 or later. If upgrade is not immediately possible, disable the Save and Continue feature in forms with File Upload fields and ensure email notifications are not configured to attach uploaded files.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5192 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5192 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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