FormcraftWordPress extension · Ncrafts
CVE-2017-18600
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 formcraft3 plugin before 3.4 for WordPress has stored XSS via the "New Form > Heading > Heading Text" field.
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 formcraft3 WordPress plugin before version 3.4 contains a stored Cross-Site Scripting (XSS) vulnerability in the 'New Form > Heading > Heading Text' field. Attackers can inject malicious JavaScript payloads that persist in the database and execute when administrators or other users view the affected form pages.
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
<= 3.2.31CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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.
-
Check formcraft3 plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate 'Formcraft - Form Builder' or 'Ncrafts Formcraft'. Compare the installed version number against the affected range (<= 3.2.31).Affected if The installed version is 3.2.31 or lower.
-
Identify existing formsIn WordPress admin, look for a 'Formcraft' or 'Forms' menu item. List all saved forms to determine if any forms have been created.Affected if Any forms exist in the system, regardless of content.
-
Inspect Heading Text field for suspicious contentOpen each existing form in the form editor. Navigate to Form Settings > Heading > Heading Text. Visually inspect the heading text for unusual characters, script tags, or payloads containing <script>, javascript:, onerror, or other XSS vectors.Affected if The Heading Text field contains any JavaScript code, HTML tags, or suspicious encoded content.
-
Query database for stored XSS payloadsAccess the WordPress database (via phpMyAdmin or CLI). Query the forms table (typically wp_formcraft_basic_form or similar) for records where the heading field contains patterns like <script, javascript:, onmouseover, or encoded variants.Affected if Database records contain executable JavaScript or HTML tags in heading-related fields.
You are affected if the formcraft3 plugin version is 3.2.31 or lower AND any form contains malicious content in the Heading Text field, or if suspicious entries are found in the database.
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 dataUpdate the formcraft3 plugin to version 3.4 or later, which includes proper input sanitization for the Heading Text field. Additionally, audit existing forms for any injected XSS payloads and clean the database if needed.
Fix this in Formcraft
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18600 — 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-2017-18600 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