Ultimate Product CatalogWordPress extension · Etoilewebdesign
CVE-2017-12200
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 Etoile Ultimate Product Catalog plugin 4.2.11 for WordPress has XSS in the Add Product Manually component.
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 Etoile Ultimate Product Catalog plugin version 4.2.11 for WordPress. The Add Product Manually component fails to properly sanitize user-supplied input, allowing injection of malicious scripts that execute in the context of the victim's browser when the crafted payload is rendered.
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
Ultimate Product CatalogWordPress extension
= 4.2.11CVSS 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.
-
Verify the plugin is installedAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins. Look for 'Etoile Ultimate Product Catalog' or 'Etoilewebdesign Ultimate Product Catalog' in the list of active plugins.Affected if The plugin named 'Etoile Ultimate Product Catalog' or 'Etoilewebdesign Ultimate Product Catalog' appears in the installed plugins list
-
Check the installed version numberIn the plugins list, locate the version number displayed beneath the plugin name. Alternatively, open the main plugin file (typically upcp-main.php or similar in wp-content/plugins/ultimate-product-catalog/) and inspect the plugin header comments for 'Version: 4.2.11'.Affected if The installed version is exactly 4.2.11 (this vulnerability affects only this specific version)
-
Confirm Add Product Manually component is accessibleCheck if the plugin admin menu includes product creation functionality. Look for menu items such as 'Add Product', 'Add New Product', or a products section where manual entry is possible. This component is located in the plugin admin interface under the catalog management section.Affected if The Add Product Manually or Add New Product feature is present and accessible within the plugin admin interface
A user is affected if they have the Etoile Ultimate Product Catalog plugin installed with version exactly 4.2.11 AND the Add Product Manually component is enabled and accessible in their WordPress admin area.
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 dataApply proper input validation and output escaping (using WordPress functions like esc_html(), esc_attr(), or wp_kses_post()) to all user inputs in the Add Product Manually component before rendering them in the page.
Fix this in Ultimate Product Catalog
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12200 — 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-12200 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