CVE-2024-12264
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe PayU CommercePro Plugin for WordPress has a critical privilege escalation vulnerability in versions up to 3.8.3. The /wp-json/payu/v1/generate-user-token and /wp-json/payu/v1/get-shipping-cost REST API endpoints fail to validate user identity before setting user IDs and authentication cookies, enabling unauthenticated attackers to create administrative accounts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify PayU CommercePro Plugin installationNavigate to WordPress Admin > Plugins and look for 'PayU CommercePro' or check the plugin files in /wp-content/plugins/ for a payu-commercpro folderAffected if The PayU CommercePro Plugin is installed on the WordPress site
-
Determine installed plugin versionIn WordPress Admin > Plugins, click on the plugin to view details and find the version number, or inspect the main plugin PHP file for a 'Version:' headerAffected if The installed version is 3.8.3 or earlier (versions up to and including 3.8.3 are affected)
-
Test vulnerable REST API endpointsSend a GET request to /wp-json/payu/v1/generate-user-token and /wp-json/payu/v1/get-shipping-cost using curl or a browser (no authentication required)Affected if The endpoints return a successful response without requiring authentication (indicates the vulnerability is present and exploitable)
-
Review administrative user accountsNavigate to WordPress Admin > Users and examine all accounts with Administrator role. Check user registration dates and email addresses for suspicious entriesAffected if There are administrative accounts that were created without authorization or that you did not create yourself
A site is affected if the PayU CommercePro Plugin versions 3.8.3 or earlier are installed AND the vulnerable REST API endpoints respond without authentication, or if unauthorized admin accounts exist.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the PayU CommercePro Plugin to version 3.8.4 or later. Review existing administrative user accounts for unauthorized access and consider implementing additional authentication checks on REST API endpoints.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12264 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-12264 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data