CVE-2025-13764
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 WP CarDealer plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.2.16. This is due to the 'WP_CarDealer_User::process_register' function not restricting what user roles a user can register with. This makes it possible for unauthenticated attackers to supply the 'administrator' role during registration and gain administrator access to the site.
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 WP CarDealer WordPress plugin contains a privilege escalation vulnerability in the process_register function which fails to validate or restrict the user role parameter during registration. Unauthenticated attackers can explicitly specify the 'administrator' role in their registration request and immediately gain full administrative access to the WordPress site.
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.
-
Confirm WP CarDealer plugin is installedNavigate to WordPress Admin > Plugins and locate 'WP CarDealer' in the list of installed plugins. Note the installed version number displayed next to the plugin name.Affected if The plugin is present in the plugins list
-
Check WordPress user registration settingGo to WordPress Admin > Settings > General and locate the 'Membership' setting. Verify whether 'Anyone can register' is enabled.Affected if Anyone can register is checked and the role is set to Subscriber, Contributor, Author, or Editor (any role that can be overridden)
-
Verify the plugin registration endpoint is accessibleAttempt to access the registration form provided by WP CarDealer, typically found at /wp-car-dealer-register/ or similar URL on the site frontend. Check if the form loads and accepts role parameters.Affected if The registration form loads and allows role selection or submission
-
Audit administrator accounts for unauthorized usersNavigate to WordPress Admin > Users and review the list of users with Administrator role. Verify each account was created by a known administrator and check the account creation date.Affected if There are administrator accounts that were not created by known site administrators or that appeared recently without explanation
A site is affected if WP CarDealer plugin is installed, WordPress user registration is enabled, and the plugin registration form is publicly accessible, allowing any visitor to register with administrator privileges.
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 WP CarDealer plugin to a patched version once available. If no patched version exists, disable the plugin until a fix is released, as the vulnerability is exploitable by any unauthenticated user.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13764 — 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-2025-13764 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