Skip to main content
Menu
CVEs

WPC Smart Messages for WooCommerce information disclosure via unauthorized shortcodes

Affects WPC Smart Messages for WooCommerce before 4.3.6 when its shortcodes are embedded in a published post. Fixed in 4.3.6.

CVE-2026-134126Published November 20, 2026, updated

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.3.6
Who is exposed
Specific setups only

Summary

The WPC Smart Messages for WooCommerce plugin lets attackers with Contributor or Author accounts read private data, including customer billing details stored as post meta and private or draft product descriptions and purchase notes. Attackers can reach it remotely over the network by embedding the plugin's shortcodes in a published post, which exposes the data to anyone who visits the page.

Written by a model

Original description

WPC Smart Messages for WooCommerce plugin before 4.3.6 contains a missing authorization vulnerability that allows authenticated attackers with Contributor or Author privileges to disclose arbitrary post meta and private product data by supplying attacker-controlled id and key attributes to the [wpcsm_product_field] and [wpcsm_product_data] shortcodes without any capability or protected-meta checks. Attackers can embed these shortcodes in a published post to exfiltrate sensitive order data such as billing email, phone, and address stored as post meta, as well as private or draft product descriptions and purchase notes, exposing confidential customer and business information to unauthenticated site visitors.

Who should check

Sites running WPC Smart Messages for WooCommerce before 4.3.6 on WordPress with WooCommerce, especially those with Contributor or Author accounts

“WPC Smart Messages for WooCommerce plugin before 4.3.6”

vulncheck.com

What to do

  1. Check whether your setup matches what the bug needs.

    WPC Smart Messages for WooCommerce installed at a version before 4.3.6 Shortcodes [wpcsm_product_field] or [wpcsm_product_data] embedded in a published post
  2. Upgrade to a fixed version: 4.3.6.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134126 (WPC Smart Messages for WooCommerce before 4.3.6 Information Disclosure via Shortcodes), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134126 (entry last updated 2026-11-20):
Affected:
- wpclever WPC Smart Messages for WooCommerce: fixed in 4.3.6
Fixed versions: 4.3.6.
Conditions (all must be true for the bug to be hit):
- WPC Smart Messages for WooCommerce installed at a version before 4.3.6 (source: https://www.vulncheck.com/advisories/wpc-smart-messages-for-woocommerce-before-information-disclosure-via-shortcodes)
- Shortcodes [wpcsm_product_field] or [wpcsm_product_data] embedded in a published post (source: https://www.vulncheck.com/advisories/wpc-smart-messages-for-woocommerce-before-information-disclosure-via-shortcodes)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134126 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134126 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://wordpress.org/plugins/wpc-smart-messages/#developers
- https://www.vulncheck.com/advisories/wpc-smart-messages-for-woocommerce-before-information-disclosure-via-shortcodes
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134126
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134126"}.

Affected versions

cve.now Index

15Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 22 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

Questions about CVE-2026-134126

Is CVE-2026-134126 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The shortcodes [wpcsm_product_field] and [wpcsm_product_data] can be embedded in a published post to read arbitrary post meta and private product data, such as billing details, private or draft product descriptions, and purchase notes, and expose it to site visitors. The impact is described as affecting authenticated low-privilege users.

Source: vulncheck.com

Which versions are affected by CVE-2026-134126?

WPC Smart Messages for WooCommerce: before 4.3.6.

Source: cve.now feed data

Am I affected, and how do I check?

Versions of WPC Smart Messages for WooCommerce before 4.3.6 are in the affected range. The setup involves the [wpcsm_product_field] or [wpcsm_product_data] shortcodes embedded in a published post; the plugin version can be checked on the Plugins screen in the WordPress admin.

Source: vulncheck.com

How do I fix CVE-2026-134126?

Update WPC Smart Messages for WooCommerce to version 4.3.6 or later. No separate vendor patch identifiers are given.

Source: vulncheck.com

Why do the sources disagree?

The sources differ on the attack requirements. The CVSS vector lists PR:L, meaning low privileges are required, while the description is noted as describing an unauthenticated vector. The impact text describes authenticated low-privilege users.

Source: vulncheck.com

No corrections so far. Something wrong on this page? Report an error.