CVE-2022-50972
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 · uneditedWooCommerce 7.1.0 contains a remote code execution vulnerability that allows attackers to execute arbitrary PHP code by injecting shell commands through the product-type parameter. Attackers can send requests to the class-wc-meta-box-product-images.php endpoint with unsanitized product-type values to write malicious PHP files to the web root.
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 confidenceWooCommerce 7.1.0 has a remote code execution vulnerability in class-wc-meta-box-product-images.php where the product-type parameter accepts unsanitized user input. Attackers inject shell commands through this parameter to write malicious PHP files to the web root, achieving arbitrary code execution.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Identify WooCommerce versionCheck the installed WooCommerce version via WordPress admin dashboard (Plugins > WooCommerce) or by reading the main plugin file header in wp-content/plugins/woocommerce/woocommerce.phpAffected if The installed version is WooCommerce 7.1.0 or falls within an unpatched version range
-
Verify vulnerable file existsConfirm class-wc-meta-box-product-images.php exists in the WooCommerce includes/admin directory path: wp-content/plugins/woocommerce/includes/admin/class-wc-meta-box-product-images.phpAffected if The vulnerable file is present and the WooCommerce version is unpatched
-
Inspect web root for unauthorized PHP filesSearch the document root (public_html or web root directory) for newly created PHP files with suspicious names (e.g., shell scripts, base64-encoded files, or files with random alphanumeric names) that were not deliberately uploadedAffected if Unexpected PHP files exist in the web root that were not intentionally created by administrators
-
Review access logs for malicious product-type parameterExamine web server access logs (Apache error/access logs or Nginx access logs) for POST/GET requests to product admin pages where the product-type parameter contains shell metacharacters (|, ;, $, &, `, etc.) or base64-encoded commandsAffected if Logs show requests with shell command injection attempts through the product-type parameter
A user is affected if they are running WooCommerce 7.1.0 (or an unpatched version) and have evidence of malicious PHP files in the web root or suspicious patterns in server logs involving the product-type parameter.
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 dataImmediately upgrade to a patched WooCommerce version; implement strict input validation and sanitization on the product-type parameter and disable file write operations from user-controlled paths.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-50972 — 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-2022-50972 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