CformsiiWordPress extension · Cformsii Project
CVE-2017-18559
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 cforms2 plugin before 14.13.3 for WordPress has multiple XSS issues.
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 cforms2 WordPress plugin before version 14.13.3 contains multiple stored Cross-Site Scripting (XSS) vulnerabilities. Attackers can inject malicious JavaScript through form fields that are not properly sanitized before being stored and displayed to other users.
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
CformsiiWordPress extension
< 14.13.3CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Locate the cforms2 plugin installationNavigate to WordPress admin dashboard under Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for a folder named 'cforms2' or 'Cformsii'.Affected if The cforms2 or Cformsii plugin folder exists in the WordPress plugins directory.
-
Identify the installed version numberIn the WordPress Plugins admin page, locate the cforms2 plugin entry and read the version number displayed beneath the plugin name. Alternatively, open the main plugin file (e.g., cforms2.php) and look for the version comment header.Affected if The reported version number is lower than 14.13.3 (e.g., 14.13.2, 14.12, etc.).
-
Confirm the plugin is activeIn WordPress admin under Plugins > Installed Plugins, verify that the cforms2 plugin status shows 'Active'.Affected if The plugin is active and running on the WordPress site.
-
Verify form creation functionality is in useCheck if any forms have been created using cforms2 by navigating to the cforms2 settings page in the WordPress admin dashboard, or by querying the WordPress database for entries in the relevant cforms tables (if accessible).Affected if One or more cforms2 forms exist and are configured on the site, as the XSS payload is injected through form field submissions.
A user is affected if the cforms2/Cformsii WordPress plugin is installed, active, and the installed version is below 14.13.3, with at least one form configured to accept submissions.
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 data14.13.3
Update the cforms2 plugin to version 14.13.3 or later to remediate the XSS vulnerabilities. If immediate update is not possible, disable the plugin until the patch can be applied.
Fix this in Cformsii
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18559 — 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-18559 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