# CVE-2020-28339: The usc-e-shop (aka Collne Welcart e-Commerce) plugin before 1.9.36 for WordPress allows Object Injection because of usces_unserialize.


- **Severity:** High 7.5 (`CVSS:3.1/AC:H/AV:N/A:H/C:H/I:H/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 7 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vh49-3q2g-93gh

## What is CVE-2020-28339?

CVE-2020-28339 is a high-severity vulnerability in n/a, published on 7 Nov 2020. 

### Official description

The usc-e-shop (aka Collne Welcart e-Commerce) plugin before 1.9.36 for WordPress allows Object Injection because of usces_unserialize. There is not a complete POP chain.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2020-28339?

It affects 1 product.


Products: Welcart Welcart E-Commerce.

## How do I fix CVE-2020-28339?

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

## Is CVE-2020-28339 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-5952](https://insights.sbomify.com/CVE-2023-5952/): Welcart e-Commerce < 2.9.5 - Unauthenticated PHP Object Injection (critical 9.8)
- [CVE-2024-42404](https://insights.sbomify.com/CVE-2024-42404/): SQL injection in Welcart e-Commerce (high 8.8)
- [CVE-2023-5953](https://insights.sbomify.com/CVE-2023-5953/): Welcart e-Commerce < 2.9.5 - Subscriber+ Arbitrary File Upload (high 8.8)
- [CVE-2023-43610](https://insights.sbomify.com/CVE-2023-43610/): SQL injection in Welcart e-Commerce (high 8.8)
- [CVE-2022-4237](https://insights.sbomify.com/CVE-2022-4237/): Welcart e-Commerce < 2.8.6 - Subscriber+ PHAR Deserialisation (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-28339 and fix it if it is affected.

What it is: CVE-2020-28339 is a high-severity vulnerability in n/a, published on 7 Nov 2020. 
Exploitation: There is no known exploitation of CVE-2020-28339 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-2020-28339/ (Markdown: https://insights.sbomify.com/CVE-2020-28339/index.md)
```

## Sources

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

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