ForminatorWordPress extension · Incsub
CVE-2024-31857
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 · uneditedForminator prior to 1.15.4 contains a cross-site scripting vulnerability. If this vulnerability is exploited, a remote attacker may obtain user information etc. and alter the page contents on the user's web browser.
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 confidenceForminator plugin versions prior to 1.15.4 contain a cross-site scripting (XSS) vulnerability. The vulnerability allows remote attackers to inject malicious scripts through unspecified input vectors, potentially enabling session hijacking, user information theft, and modification of page content in victim browsers.
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
< 1.15.4CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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.
-
Verify Forminator plugin is installedLog into WordPress admin dashboard and navigate to Plugins > Installed Plugins, or check /wp-content/plugins/forminator/ directory exists on the serverAffected if Forminator plugin is present in the WordPress installation
-
Locate the installed Forminator version numberIn WordPress admin, go to Plugins > Installed Plugins and find the version number listed under the Forminator plugin entry. Alternatively, inspect the main plugin file (e.g., /wp-content/plugins/forminator/forminator.php) and look for the 'Version' header in the file commentsAffected if A version number is displayed or found in the plugin header
-
Compare installed version against the affected rangeCompare the found version number to 1.15.4. Any version lower than 1.15.4 (such as 1.15.3, 1.14.0, 1.13.0, etc.) falls within the affected rangeAffected if The installed version is numerically less than 1.15.4 (for example, 1.15.3, 1.14.2, or any 1.x version prior to 1.15.4)
A user is affected if the Forminator plugin is installed and the installed version is any release prior to version 1.15.4.
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.
dbcve · scoped1.15.4
Upgrade Forminator to version 1.15.4 or later to obtain the patched version. If immediate upgrade is not possible, consider disabling the plugin or implementing Web Application Firewall rules to filter malicious request patterns.
1.15.4
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find Forminator in the plugin list
- Click 'Update now' if an update is available, or manually update to version 1.15.4 or later
- Verify the update completed successfully
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Forminator
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31857 — 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-2024-31857 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