# CVE-2024-2382: Business logic in Authorize.net Payment Gateway For WooCommerce

> Unauthenticated attackers can bypass payment verification to mark orders as paid, affecting WooCommerce stores using this plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 4 Jun 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-5wfj-9rwm-6f4w

## What is CVE-2024-2382?

CVE-2024-2382 is a medium-severity vulnerability in ishanverma Authorize.net Payment Gateway For WooCommerce, published on 4 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Authorize.net Payment Gateway For WooCommerce plugin for WordPress is vulnerable to payment bypass in all versions up to, and including, 8.0. This is due to the plugin not properly verifying the authenticity of the request that updates a orders payment status. This makes it possible for unauthenticated attackers to update order payment statuses to paid bypassing any payment.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2024-2382 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-2382 is a medium-severity vulnerability in ishanverma Authorize.net Payment Gateway For WooCommerce, published on 4 Jun 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-2024-2382 in the wild and no public exploit code.

Affected product: ishanverma Authorize.net Payment Gateway 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-2024-2382/ (Markdown: https://insights.sbomify.com/CVE-2024-2382/index.md)
```

## Sources

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

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