# CVE-2023-49194: WordPress Importify (Dropshipping WooCommerce) plugin <= 1.0.4 - Sensitive Data Exposure vulnerability

> Attackers can retrieve embedded sensitive data due to information insertion into debugging code in the Importify WordPress plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Dec 2024
- **Updated:** 29 Apr 2026
- **Also known as:** GHSA-7v28-88f9-8882

## What is CVE-2023-49194?

CVE-2023-49194 is a medium-severity vulnerability in Importify (Dropshipping WooCommerce), published on 9 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insertion of Sensitive Information Into Debugging Code vulnerability in importify Importify (Dropshipping WooCommerce) importify allows Retrieve Embedded Sensitive Data.This issue affects Importify (Dropshipping WooCommerce): from n/a through <= 1.0.4.

Weakness: CWE-215 (Insertion of Sensitive Information Into Debugging Code)

## Which versions are affected by CVE-2023-49194?


## How do I fix CVE-2023-49194?

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

## Is CVE-2023-49194 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-49194 and fix it if it is affected.

What it is: CVE-2023-49194 is a medium-severity vulnerability in Importify (Dropshipping WooCommerce), published on 9 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-49194 in the wild and no public exploit code.

Affected product: Importify (Dropshipping 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-2023-49194/ (Markdown: https://insights.sbomify.com/CVE-2023-49194/index.md)
```

## Sources

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

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