FormcraftWordPress extension · Ncrafts
CVE-2019-5920
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 · uneditedCross-site request forgery (CSRF) vulnerability in FormCraft 1.2.1 and earlier allows remote attackers to hijack the authentication of administrators via a specially crafted page.
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 confidenceCSRF vulnerability in FormCraft plugin versions 1.2.1 and earlier allows remote attackers to hijack administrator authentication by tricking logged-in admins into visiting specially crafted malicious pages that trigger unauthorized admin actions.
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.1CVSS 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 plugin installationSearch for FormCraft plugin files in the WordPress plugins directory (wp-content/plugins/) or check the site's plugin inventoryAffected if FormCraft plugin is found installed on the system
-
Identify the installed FormCraft versionCheck the plugin header (usually in main PHP file or readme.txt) for the version number, or query the plugin version via admin dashboard if accessibleAffected if Version is 1.2.1 or earlier
-
Verify CSRF protection on admin formsInspect the source code of admin-facing forms in FormCraft (look for wp_nonce_field, wp_nonce, nonce_field, or similar nonce verification calls in form definitions)Affected if Admin forms lack nonce/token verification logic in the code
-
Check AJAX endpoints for nonce validationExamine FormCraft AJAX handlers (admin-ajax.php calls within the plugin) for nonce verification using check_ajax_referer or wp_verify_nonceAffected if AJAX endpoints used by the plugin do not validate nonces
-
Confirm active administrator session availabilityDetermine if any administrator accounts exist and have active sessions, as the attack requires a logged-in adminAffected if Administrators have active sessions on the site
A user is affected if the FormCraft plugin version 1.2.1 or earlier is installed AND the admin forms/AJAX endpoints lack nonce/CSRF token verification.
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 dataImplement anti-CSRF tokens (nonce verification) on all admin-facing forms and AJAX endpoints in FormCraft, or upgrade to a patched version if available from the vendor.
Fix this in Formcraft
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5920 — 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-5920 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