dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-12126

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

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 · unedited
The WCFM Marketplace – Multivendor Marketplace for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Attachment 'post_title' in all versions up to, and including, 3.7.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Vendor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. An attacker can plant the payload by uploading a media attachment with a crafted title via the WordPress REST API (/wp-json/wp/v2/media), without ever invoking the AJAX endpoint themselves, as the unescaped title is later emitted inside DataTables JSON and inserted as innerHTML upon any privileged user loading the media dashboard.

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 confidence

The WCFM Marketplace plugin for WordPress fails to sanitize the post_title parameter when uploading media attachments via the REST API (/wp-json/wp/v2/media). The crafted title is later rendered unescaped inside DataTables JSON on the media dashboard and inserted as innerHTML, causing stored XSS to execute when privileged users access the page.

MitigationUpdate the WCFM Marketplace plugin to version 3.7.4 or later which implements proper input sanitization on attachment titles and output escaping when rendering in DataTables. Until patched, restrict Vendor-level API access and monitor media library uploads.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify WCFM Marketplace plugin is installed
    Go to WordPress admin > Plugins and confirm WCFM Marketplace is active, or check via WP-CLI: wp plugin list --name=wcfm-marketplace --status=active
    Affected if The plugin is installed and active - proceed to version check
  2. Check installed WCFM Marketplace version
    In WordPress admin, go to Plugins > WCFM Marketplace and view the version number, or run: wp plugin get wcfm-marketplace --field=version
    Affected if Version is unknown, older than 3.7.4, or you cannot confirm the version is 3.7.4 or later - the vulnerability may be present
  3. Confirm REST API media endpoint is accessible
    Send a test POST request to /wp-json/wp/v2/media with valid WordPress authentication (cookie or nonce). Check if the endpoint accepts the request and returns a media ID.
    Affected if The media REST API endpoint accepts unauthenticated or low-privilege requests (Vendor-level), exposing the attack vector
  4. Verify media title renders in DataTables without encoding
    Upload a test media file via REST API with a post_title containing a benign script tag like <script>alert(1)</script>. Then access the WCFM Media dashboard and inspect the page source or network response for the raw unescaped script tag in the DataTables JSON response.
    Affected if The title renders as unescaped HTML in the media dashboard - the XSS vulnerability is confirmed present

You are affected if WCFM Marketplace is installed, the version is below 3.7.4 or unconfirmed, and the REST API media endpoint accepts uploads that render unescaped in the dashboard.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the WCFM Marketplace plugin to version 3.7.4 or later which implements proper input sanitization on attachment titles and output escaping when rendering in DataTables. Until patched, restrict Vendor-level API access and monitor media library uploads.

Recommended fix Moderate confidence

Version 3.7.4 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Find 'WCFM Marketplace – Multivendor Marketplace for WooCommerce'
  4. 4. Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org/plugins/wcfm-marketplace/
  5. 5. Verify the updated version is newer than 3.7.3
  6. 6. Test the media attachment functionality to confirm the XSS fix is applied
Caveat Minimal risk - this is a security bugfix release; verify vendor attachment functionality after update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12126 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12126 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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