Product Enquiry For WoocommerceWordPress extension · Gravitymaster
CVE-2023-47696
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 · uneditedUnauth. Stored Cross-Site Scripting (XSS) vulnerability in Gravity Master Product Enquiry for WooCommerce plugin <= 3.0 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 confidenceAn unauthenticated stored Cross-Site Scripting (XSS) vulnerability exists in the Gravity Master Product Enquiry for WooCommerce plugin versions 3.0 and earlier. The vulnerability allows attackers to inject malicious JavaScript code through plugin input fields that is then stored in the database and executed when other users 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
Product Enquiry For WoocommerceWordPress extension
<= 3.0CVSS 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.
-
Verify the plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Gravitymaster Product Enquiry For Woocommerce' or check the plugin files in wp-content/plugins/ for a directory matching gravitymaster-product-enquiry-for-woocommerceAffected if The plugin is not installed means not affected; if present, continue to version check
-
Check installed plugin versionIn WordPress admin Plugins page, click on the plugin to view its details and note the version number, or inspect the main plugin PHP file for a 'Version' header in the plugin comment blockAffected if Version 3.0 or earlier indicates the environment is within the affected range
-
Confirm product enquiry functionality is activeNavigate to WooCommerce > Settings > Products or check for a Gravitymaster enquiry form shortcode being used on product pages; verify the enquiry form is accessible to unauthenticated users on the storefrontAffected if The enquiry form is publicly accessible and accepting input, making the XSS attack surface active
-
Inspect stored enquiry data for malicious scriptsCheck the WordPress database tables where enquiry submissions are stored (typically wp_posts, wp_postmeta, or a custom table created by the plugin) for suspicious script tags, javascript: URLs, or event handlers like onload/onerror in submitted fieldsAffected if Any stored scripts found in enquiry submission data indicate active exploitation of this vulnerability
The environment is affected if the Gravitymaster Product Enquiry For Woocommerce plugin version is 3.0 or earlier and the enquiry form is publicly accessible, with potential compromise shown by malicious scripts in stored enquiry data.
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 plugin to a version newer than 3.0 if available, or apply input validation and output encoding fixes to the plugin code to sanitize user-supplied data before storage and before rendering.
Fix this in Product Enquiry For Woocommerce
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47696 — 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-47696 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