# CVE-2024-12264: PayU CommercePro Plugin <= 3.8.3 - Unauthenticated Privilege Escalation

> Unauthenticated attackers can create administrative accounts via vulnerable REST API endpoints in the PayU CommercePro WordPress plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jan 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-gpww-5rqj-3jh7

## What is CVE-2024-12264?

CVE-2024-12264 is a critical vulnerability in payuplugin PayU CommercePro Plugin, published on 7 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The PayU CommercePro Plugin plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 3.8.3. This is due to /wp-json/payu/v1/generate-user-token and /wp-json/payu/v1/get-shipping-cost  REST API endpoints not properly verifying a user's identity prior to setting the users ID and auth cookies. This makes it possible for unauthenticated attackers to create new administrative user accounts.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2024-12264 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-12264 is a critical vulnerability in payuplugin PayU CommercePro Plugin, published on 7 Jan 2025. 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-12264 in the wild and no public exploit code.

Affected product: payuplugin PayU CommercePro Plugin. 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-12264/ (Markdown: https://insights.sbomify.com/CVE-2024-12264/index.md)
```

## Sources

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

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