# CVE-2022-4107: SMSA Shipping for WooCommerce < 1.0.5 - Subscriber+ Arbitrary File Download

> Authenticated subscribers can download arbitrary files from the server due to missing authorization and file validation checks.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Dec 2022
- **Updated:** 14 Apr 2025
- **Also known as:** GHSA-2f42-3cfg-m57p

## What is CVE-2022-4107?

CVE-2022-4107 is a medium-severity missing authorization vulnerability in Unknown SMSA Shipping for WooCommerce, published on 19 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The SMSA Shipping for WooCommerce WordPress plugin before 1.0.5 does not have authorisation and proper CSRF checks, as well as does not validate the file to be downloaded, allowing any authenticated users, such as subscriber to download arbitrary file from the server

## Which versions are affected by CVE-2022-4107?

It affects 1 product.


Products: Cedcommerce Smsa Shipping for Woocommerce.

## How do I fix CVE-2022-4107?

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

## Is CVE-2022-4107 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4107 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4107 and fix it if it is affected.

What it is: CVE-2022-4107 is a medium-severity missing authorization vulnerability in Unknown SMSA Shipping for WooCommerce, published on 19 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4107 exists.

Affected product: Unknown SMSA Shipping for WooCommerce. 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-2022-4107/ (Markdown: https://insights.sbomify.com/CVE-2022-4107/index.md)
```

## Sources

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

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