CVE-2025-3105

Vehica Core <= 1.0.97 - Authenticated (Subscriber+) Privilege Escalation

2025-04-03 00:00
Alyudin Nafiie

Strategic Overview

Status
Patched in 1.0.98
Affected Plugin
Vehica Core
Affected Version
<= 1.0.97
CVSS
8.8High
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE-2025-3105
View all Vehica Core vulnerabilities

At a glance

CVE-2025-3105 is a high-severity Improper Privilege Management vulnerability in the Vehica Core WordPress plugin, affecting versions <= 1.0.97. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.0.98; sites on affected versions should update now. Disclosed April 2025, reported by Alyudin Nafiie.

Vulnerability Overview

The Vehica Core plugin for WordPress, used by the Vehica - Car Dealer & Listing WordPress Theme, is vulnerable to privilege escalation in all versions up to, and including, 1.0.97. This is due to the plugin not properly validating user meta fields prior to updating them in the database. This makes it possible for authenticated attackers, with Subscriber-level access and above, to change escalate their privileges to Administrator.

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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-269: Improper Privilege Management

Reaching this weakness in Vehica Core <= 1.0.97 takes an account at Subscriber level or above. Improper privilege management means the code lets an account end up with capabilities its role should not have.

It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For Vehica Core the fix is 1.0.98: builds <= 1.0.97 are affected, anything from 1.0.98 onward is not.

Remediation

Update to version 1.0.98, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Vehica Core 1.0.98 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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