dbcve.org
ForminatorWordPress extension · Incsub

CVE-2024-28890

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-23
Fix available
A fix is available. Upgrade to 1.29.0 or later.
See remediation →
55/100
Remediation priority · Elevated
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
Forminator prior to 1.29.0 contains an unrestricted upload of file with dangerous type vulnerability. If this vulnerability is exploited, a remote attacker may obtain sensitive information by accessing files on the server, alter the site that uses the plugin, and cause a denial-of-service (DoS) condition.

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

Forminator WordPress plugin prior to version 1.29.0 fails to properly validate or restrict file types during upload operations, allowing unauthenticated remote attackers to upload dangerous file types (such as executable scripts) that can be accessed to obtain sensitive information, modify site content, or cause denial-of-service.

MitigationUpdate Forminator plugin to version 1.29.0 or later which implements proper file type validation and upload restrictions. Verify all file upload functionality works correctly after updating.

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
ForminatorWordPress extension
Affected:< 1.29.0

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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. Verify Forminator plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Forminator' in the list. Alternatively, check the /wp-content/plugins/forminator/ directory exists on the server.
    Affected if Forminator plugin is present in the WordPress installation
  2. Check installed Forminator version
    In WordPress admin, go to Plugins > Installed Plugins and find the Forminator plugin to view its version number. Or check the version in the plugin's main PHP file header or in /wp-content/plugins/forminator/readme.txt.
    Affected if Version is lower than 1.29.0 (for example, 1.28.0, 1.27.3, etc.)
  3. Confirm file upload module is in use
    Check if any Forminator forms have file upload fields enabled. In Forminator editor, look for 'File Upload' field type in any published forms. Also check /wp-content/uploads/forminator/ directory exists and contains any uploaded files.
    Affected if Forms with file upload fields are published and publicly accessible
  4. Verify upload directory is web-accessible
    Attempt to access a known uploaded file via browser (for example, visit the upload path like /wp-content/uploads/forminator/filename.ext). Check if directory listing is enabled or if files are directly accessible without authentication.
    Affected if Uploaded files can be accessed directly via web without authentication

You are affected if Forminator plugin versions below 1.29.0 are installed AND any forms with file upload fields are publicly accessible on your site.

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 1.29.0 or later
Fixed in 1.29.0
Interim mitigation

Update Forminator plugin to version 1.29.0 or later which implements proper file type validation and upload restrictions. Verify all file upload functionality works correctly after updating.

Recommended fix High confidence

Forminator 1.29.0

  1. Backup the WordPress site and database before updating
  2. Navigate to WordPress Admin > Plugins > Installed Plugins
  3. Locate Forminator plugin and click 'Update Now' to update to version 1.29.0 or later
  4. Alternatively, use 'wp plugin update forminator' via WP-CLI if available
  5. Verify the plugin version is 1.29.0 or higher after updating

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

Fix this in Forminator Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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