# CVE-2024-37213: WordPress AliExpress Dropshipping with AliNext Lite plugin <= 3.4.6 - CSRF to XSS vulnerability

> Attackers can trick users into performing actions that lead to Cross-Site Scripting via CSRF in the AliNext Lite plugin.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **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:** 12 Jul 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-63q2-hp23-jpgh

## What is CVE-2024-37213?

CVE-2024-37213 is a high-severity vulnerability in guru-aliexpress AliNext, published on 12 Jul 2024. 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

Cross-Site Request Forgery (CSRF) vulnerability in guru-aliexpress AliNext ali2woo-lite allows Cross Site Request Forgery.This issue affects AliNext: from n/a through <= 3.4.6.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2024-37213?


## How do I fix CVE-2024-37213?

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

## Is CVE-2024-37213 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-37213 and fix it if it is affected.

What it is: CVE-2024-37213 is a high-severity vulnerability in guru-aliexpress AliNext, published on 12 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-37213 in the wild and no public exploit code.

Affected product: guru-aliexpress AliNext. 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-2024-37213/ (Markdown: https://insights.sbomify.com/CVE-2024-37213/index.md)
```

## Sources

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

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