Product Enquiry For WoocommerceWordPress extension · Gravitymaster
CVE-2023-49761
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Gravity Master Product Enquiry for WooCommerce.This issue affects Product Enquiry for WooCommerce: from n/a through 3.0.
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 Request Forgery (CSRF) vulnerability in the Product Enquiry for WooCommerce plugin allows remote attackers to induce authenticated users to execute unintended actions (such as submitting spurious product enquiry forms) by tricking them into visiting malicious web pages. The lack of proper anti-CSRF token validation on state-changing operations enables this attack.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 plugin installationCheck if the 'gravitymaster-product-enquiry-for-woocommerce' plugin directory exists in your WordPress wp-content/plugins folder, or list installed plugins via wp-cli: wp plugin list --status=activeAffected if plugin is not installed or not active
-
Confirm installed versionCheck the plugin version in the main plugin file header (usually product-enquiry-for-woocommerce.php) or via: wp plugin get product-enquiry-for-woocommerce --field=versionAffected if version is greater than 3.0
-
Inspect enquiry form for nonce fieldAccess a product enquiry form on the frontend and view page source. Search for an input field named '_wpnonce', 'nonce', or similar token identifier in the form HTMLAffected if form lacks any nonce or token input field
-
Verify AJAX handlers for nonce checkExamine plugin PHP source files for AJAX action handlers (wp_ajax_* and wp_ajax_nopriv_* hooks). Search for calls to 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' within these handlersAffected if AJAX handlers do not verify nonce tokens before processing requests
You are affected if the plugin is installed at version 3.0 or lower AND your enquiry forms lack nonce token fields AND AJAX handlers skip nonce validation.
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 dataImplement anti-CSRF tokens (nonces) for all form submissions and AJAX actions that perform state-changing operations, validate these tokens server-side on every request, and consider implementing SameSite cookie attributes. If a patched version exists, upgrade to that version immediately.
Fix this in Product Enquiry For Woocommerce
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49761 — 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-49761 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