Wcfm MarketplaceWordPress extension · Wclovers
CVE-2024-44009
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WC Lovers WCFM Marketplace wc-multivendor-marketplace allows Reflected XSS.This issue affects WCFM Marketplace: from n/a through <= 3.6.11.
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 confidenceThis is a reflected Cross-site Scripting (XSS) vulnerability in the WCFM Marketplace plugin for WordPress/WooCommerce. The vulnerability allows attackers to inject malicious JavaScript code through unsanitized user input that gets reflected back in web pages without proper encoding. This affects all versions through 3.6.11 of the wc-multivendor-marketplace plugin.
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
Wcfm MarketplaceWordPress extension
<= 3.6.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.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.
-
Locate WCFM Marketplace plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find 'WCFM Marketplace' (or wc-multivendor-marketplace), and read the version number displayed beneath the plugin nameAffected if Version is 3.6.11 or lower (any version through 3.6.11 is affected)
-
Confirm plugin is activeIn WordPress admin > Plugins > Installed Plugins, verify that WCFM Marketplace shows as 'Active' (not just installed)Affected if Plugin is active and processing requests
-
Check WordPress plugins directoryVia FTP or file manager, navigate to /wp-content/plugins/ and locate the wc-multivendor-marketplace folder. Open the main plugin file (usually wc-multivendor-marketplace.php) and read the Version: header commentAffected if Version header in plugin file reads 3.6.11 or lower
-
Query database for exact versionAccess WordPress database via phpMyAdmin or CLI, query the wp_options table for option_name = 'wcfm_plugin_version' or similar version option; alternatively query wp_posts for post_type = 'wcfm_vendor' to confirm marketplace data existsAffected if Stored version is 3.6.11 or lower, indicating the vulnerable release is installed
You are affected if WCFM Marketplace plugin version is 3.6.11 or lower and the plugin is active on your WordPress/WooCommerce site.
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 WCFM Marketplace to the latest available version (3.6.12 or later) which should include proper input sanitization/encoding. As an interim measure, implement a Web Application Firewall (WAF) rule to block XSS attack patterns in requests.
Fix this in Wcfm Marketplace
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-44009 — 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-2024-44009 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