CVE-2024-12264

PayU CommercePro Plugin <= 3.8.3 - Unauthenticated Privilege Escalation

2025-01-06 16:09
wesley (wcraft)

Strategic Overview

Status
Patched in 3.8.4
Affected Plugin
PayU India
Affected Version
<= 3.8.3
CVSS
9.8Critical
Weakness type
CWE-287 · Improper Authentication
CVE
CVE-2024-12264
View all PayU India vulnerabilities

At a glance

CVE-2024-12264 is a critical-severity Improper Authentication vulnerability in the PayU India WordPress plugin, affecting versions <= 3.8.3. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.8.4; sites on affected versions should update now. Disclosed January 2025, reported by wesley (wcraft).

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-287: Improper Authentication

Reaching this weakness in PayU India <= 3.8.3 takes no account at all. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.

An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For PayU India the fix is 3.8.4: builds <= 3.8.3 are affected, anything from 3.8.4 onward is not.

Remediation

Update to version 3.8.4, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: PayU India 3.8.4 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-12264https://www.wordfence.com/threat-intel/vulnerabilities/id/bf037e4a-2dd7-4296-b86b-635901d2d68fhttps://nvd.nist.gov/vuln/detail/CVE-2024-12264

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C