FormcraftWordPress extension · Ncrafts
CVE-2023-22717
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 · uneditedAuth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in nCrafts FormCraft plugin <= 1.2.6 versions.
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in the nCrafts FormCraft WordPress plugin allows authenticated users with contributor-level or higher permissions to inject malicious JavaScript into form submissions. The injected script executes in the browsers of other users who view the affected content.
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.6CVSS 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.
-
Verify FormCraft plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'FormCraft' or 'Ncrafts Formcraft' in the listAffected if The FormCraft plugin appears in the installed plugins list
-
Check installed FormCraft versionIn the Plugins list, find FormCraft and note the version number displayed under the plugin name. Alternatively, check the plugin's main PHP file header for 'Version:' tagAffected if The installed version is 1.2.6 or lower
-
Confirm plugin is activeIn Plugins > Installed Plugins, check if FormCraft shows 'Active' status under the plugin nameAffected if The plugin is active and the version is 1.2.6 or lower
-
Identify users with contributor-level or higher accessGo to Users > All Users in WordPress admin and note users with roles of Contributor, Author, Editor, or AdministratorAffected if Any users exist with Contributor, Author, Editor, or Administrator roles while FormCraft <=1.2.6 is active
-
Review FormCraft form submissions for suspicious contentAccess FormCraft submissions panel (usually under FormCraft menu in admin) and inspect recent entries for unusual characters like <script>, javascript:, onerror=, or HTML tags in form fieldsAffected if Form submissions contain unescaped HTML or JavaScript code
You are affected if FormCraft (Ncrafts Formcraft) version 1.2.6 or lower is installed and active on your WordPress site, particularly if you have users with contributor-level or higher permissions.
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 FormCraft plugin to a version newer than 1.2.6. If no patched version is available, implement input validation/sanitization on form fields and consider restricting user permissions until a fix is available.
Fix this in Formcraft
Scoped from the published advisory
- Consultation3.0 h
- Implementation3.0 h
- Testing2.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22717 — 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-2023-22717 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