CVE-2026-1722
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 WCFM Marketplace – Multivendor Marketplace for WooCommerce plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.7.0. This is due to the plugin not implementing authorization checks in the `wcfm-refund-requests-form` AJAX controller. This makes it possible for unauthenticated attackers to create arbitrary refund requests for any order ID and item ID, potentially leading to financial loss if automatic refund approval is enabled in the plugin settings.
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 WCFM Marketplace plugin for WooCommerce contains an Insecure Direct Object Reference (IDOR) vulnerability in its `wcfm-refund-requests-form` AJAX controller. The plugin fails to verify user authorization before processing refund requests, allowing unauthenticated attackers to submit arbitrary refund requests for any order ID and item ID. When automatic refund approval is enabled, this can result in unauthorized financial transactions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Confirm WCFM Marketplace plugin is installedNavigate to WordPress admin > Plugins and locate WCFM Marketplace, or check the plugin version file in /wp-content/plugins/wcfm-marketplace/Affected if Plugin is installed and active
-
Check installed plugin versionView the plugin version from the WordPress plugins list or read the main plugin file headerAffected if Installed version is lower than 3.7.1
-
Verify AJAX endpoint is accessibleThe vulnerable endpoint is /wp-admin/admin-ajax.php?action=wcfm-refund-requests-form. Test if the endpoint responds (requires plugin to be active)Affected if Endpoint returns a response (plugin is active and vulnerable version may be in use)
-
Inspect automatic refund approval settingGo to WCFM > Settings > Refund tab and locate the automatic refund approval option, or inspect the database option for wcfm_refund_auto_approveAffected if Automatic refund approval is enabled (this is the condition that makes the IDOR exploitable for financial impact)
A user is affected if WCFM Marketplace version is below 3.7.1 AND automatic refund approval is enabled, allowing unauthenticated IDOR attacks to trigger unauthorized refunds.
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 WCFM Marketplace plugin to version 3.7.1 or later which includes proper authorization checks. Additionally, disable automatic refund approval in plugin settings as a defense-in-depth measure until the update is applied.
- Consultation3.0 h
- Implementation2.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,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1722 — 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-2026-1722 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