# CVE-2017-18356: Code injection in n/a

> A shop manager can trigger PHP object injection via crafted strings in WooCommerce shortcodes, potentially leading to code execution.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jan 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vwrr-q8r4-3hgf

## What is CVE-2017-18356?

CVE-2017-18356 is a high-severity code injection vulnerability in n/a, published on 15 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In the Automattic WooCommerce plugin before 3.2.4 for WordPress, an attack is possible after gaining access to the target site with a user account that has at least Shop manager privileges. The attacker then constructs a specifically crafted string that will turn into a PHP object injection involving the includes/shortcodes/class-wc-shortcode-products.php WC_Shortcode_Products::get_products() use of cached queries within shortcodes.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2017-18356?

It affects 1 product.


Products: Woocommerce Woocommerce.

## How do I fix CVE-2017-18356?

No fix has been published for CVE-2017-18356 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-18356 being exploited?

There is no known exploitation of CVE-2017-18356 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2019-20891](https://insights.sbomify.com/CVE-2019-20891/): WooCommerce Cross-Site Request Forgery (CSRF) (high 8.8)
- [CVE-2018-20714](https://insights.sbomify.com/CVE-2018-20714/): Path traversal in n/a (high 8.1)
- [CVE-2025-5062](https://insights.sbomify.com/CVE-2025-5062/): WooCommerce <= 9.4.2 - PostMessage-Based Cross-Site Scripting (medium 6.1)
- [CVE-2019-9168](https://insights.sbomify.com/CVE-2019-9168/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2015-2329](https://insights.sbomify.com/CVE-2015-2329/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-18356 and fix it if it is affected.

What it is: CVE-2017-18356 is a high-severity code injection vulnerability in n/a, published on 15 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-18356 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-18356/ (Markdown: https://insights.sbomify.com/CVE-2017-18356/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-18356
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-18356
- OSV: https://osv.dev/vulnerability/CVE-2017-18356

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-18356/
Summaries are generated and may contain mistakes; the official description above is the record.