FormcraftWordPress extension · Ncrafts
CVE-2019-15114
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 formcraft-form-builder plugin before 1.2.2 for WordPress has CSRF.
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 confidenceThe formcraft-form-builder WordPress plugin before version 1.2.2 contains a Cross-Site Request Forgery (CSRF) vulnerability that allows attackers to craft malicious requests targeting authenticated administrators, potentially leading to unauthorized form configuration changes or data submission.
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
FormcraftWordPress extension
< 1.2.2CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Formcraft Form Builder plugin filesNavigate to wp-content/plugins/ in your WordPress installation directory and check for a folder named 'formcraft-form-builder' or similar Formcraft-related foldersAffected if The plugin folder exists in the plugins directory
-
Identify the installed plugin versionOpen the main plugin PHP file (usually named formcraft-form-builder.php or similar) and look for the 'Version' header in the plugin comment block at the top of the fileAffected if The version number displayed is lower than 1.2.2 (for example, 1.2.1, 1.2.0, 1.1.x, etc.)
-
Verify the plugin is activeLog into the WordPress admin dashboard, go to Plugins > Installed Plugins, and check if the Formcraft Form Builder plugin shows as 'Active'Affected if The plugin is active and the version is below 1.2.2
-
Confirm WordPress admin authentication requirementThis CSRF vulnerability requires an authenticated administrator to trigger the malicious request. Check if any administrator sessions exist or if the site has admin users with form-building privilegesAffected if The site has active administrator accounts with access to the Formcraft plugin functionality and the installed version is below 1.2.2
You are affected if the Formcraft Form Builder plugin is installed and active with a version lower than 1.2.2, as the CSRF flaw allows attackers to exploit authenticated administrator sessions.
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 data1.2.2
Update the formcraft-form-builder plugin to version 1.2.2 or later to remediate the CSRF vulnerability.
Fix this in Formcraft
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15114 — 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-2019-15114 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