# CVE-2026-113617: Automated Import Products to Cart < 1.0.4 - Subscriber+ Arbitrary File Read and Deletion via Path Traversal


- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-cmrc-7c99-5736

## What is CVE-2026-113617?

CVE-2026-113617 is a critical vulnerability in Unknown Automated Import Products to Cart, published on 29 Oct 2026. 

### Official description

The Automated Import Products to Cart WordPress plugin before 1.0.4 does not sanitize a user-supplied file path before using it to read and delete files, allowing users with minimal permissions, such as subscribers, to read arbitrary files (including ones containing the database credentials) and delete arbitrary files on the server.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-113617?


## How do I fix CVE-2026-113617?

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

## Is CVE-2026-113617 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-113617 and fix it if it is affected.

What it is: CVE-2026-113617 is a critical vulnerability in Unknown Automated Import Products to Cart, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113617 in the wild and no public exploit code.

Affected product: Unknown Automated Import Products to Cart. 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-2026-113617/ (Markdown: https://insights.sbomify.com/CVE-2026-113617/index.md)
```

## Sources

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

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