GnucommerceWordPress extension · Sir
CVE-2017-18572
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 gnucommerce plugin before 1.4.2 for WordPress has XSS.
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 confidenceCross-Site Scripting (XSS) vulnerability in the gnucommerce WordPress plugin affecting versions prior to 1.4.2. The vulnerability allows attackers to inject malicious scripts into web pages viewed by 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
GnucommerceWordPress extension
< 1.4.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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/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 gnucommerce plugin filesNavigate to wp-content/plugins/ in your WordPress installation directory and look for a folder named 'gnucommerce' or 'sir-gnucommerce'. If the folder exists, the plugin is installed.Affected if The plugin folder exists in wp-content/plugins/
-
Identify the installed plugin versionOpen the main plugin file (usually plugin-name.php) in a text editor and look for the version declaration in the plugin header comment, typically found at the top of the file as 'Version: x.x.x' or in the readme.txt file.Affected if The version listed is less than 1.4.2 (for example, 1.4.1, 1.4.0, 1.3.x, etc.)
-
Check if the plugin is activeLog into the WordPress admin dashboard, go to Plugins > Installed Plugins, and look for gnucommerce or Sir Gnucommerce in the list. Check if it shows 'Active' status.Affected if The plugin shows as Active and the version is below 1.4.2
-
Verify WordPress admin access to confirm scopeIn the WordPress admin, navigate to the plugin settings page (usually under Settings > gnucommerce or a dedicated gnucommerce admin menu item) to confirm the plugin is fully functional and not just installed.Affected if The plugin settings page loads and the plugin is operational with a version below 1.4.2
Your environment is affected if the gnucommerce (Sir Gnucommerce) WordPress plugin is installed, active, and running at a version lower than 1.4.2, as this version range contains the XSS vulnerability that could allow script injection.
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.4.2
Update gnucommerce plugin to version 1.4.2 or later. If unable to update immediately, disable the plugin until a patch can be applied.
Fix this in Gnucommerce
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18572 — 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-18572 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