# CVE-2022-4794: AAWP < 3.12.3 - Unsafe URL Handling

> Attackers can abuse trusted domains to load malware via reflected file download, bypassing corporate firewall rules.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 30 Jan 2023
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-3242-hvmp-wgvm

## What is CVE-2022-4794?

CVE-2022-4794 is a high-severity vulnerability in Unknown AAWP, published on 30 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The AAWP WordPress plugin before 3.12.3 can be used to abuse trusted domains to load malware or other files through it (Reflected File Download) to bypass firewall rules in companies.

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

It affects 1 product.


Products: Getaawp Amazon Affiliate Wordpress Plugin.

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

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

## Is CVE-2022-4794 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4794 is a high-severity vulnerability in Unknown AAWP, published on 30 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4794 exists.

Affected product: Unknown AAWP. 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-4794/ (Markdown: https://insights.sbomify.com/CVE-2022-4794/index.md)
```

## Sources

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

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