dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-3105

HIGH · 8.8 CVSS v3.1 Published 2025-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
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 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 confidence

The Vehica Core WordPress plugin fails to properly validate user meta fields before updating them in the database, allowing authenticated users with Subscriber-level permissions to manipulate their own user meta to escalate privileges to Administrator.

MitigationUpdate the Vehica Core plugin to version 1.0.98 or later. Until the patch is applied, consider disabling the plugin or restricting user registration.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Vehica Core plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Vehica Core' in the list of installed plugins. Note whether it is active or inactive.
    Affected if The plugin is installed and active in the WordPress environment.
  2. Identify the installed plugin version
    In the Plugins list, click on 'Vehica Core' to view the plugin details, or check the plugin header in wp-content/plugins/vehica-core/vehica-core.php for the 'Version' defined constant.
    Affected if The installed version is lower than 1.0.98 (e.g., 1.0.97, 1.0.96, etc.).
  3. Verify if WordPress user registration is enabled
    Go to WordPress admin > Settings > General and check the 'Membership' setting: 'Anyone can register'. Also check wp-config.php for DISALLOW_FILE_MODS or custom registration settings.
    Affected if User registration is enabled, allowing new Subscriber-level accounts to be created.
  4. Check for existing Subscriber-level users
    Navigate to WordPress admin > Users and look for any users with the 'Subscriber' role. Note the total number of users with low-privilege roles.
    Affected if There are one or more Subscriber-level users present in the system.
  5. Inspect user meta update capabilities
    Review the plugin code in vehica-core/includes/Endpoints folder for endpoints that handle user meta updates (such as SaveUserMeta or similar). Verify if these endpoints allow modification of user role or capability fields like 'wp_capabilities'.
    Affected if The plugin exposes an API endpoint that accepts and processes role or capability changes in user meta without proper authorization checks.

You are affected if the Vehica Core plugin is installed and active with a version lower than 1.0.98, user registration is enabled, and the plugin exposes user meta update functionality without validating that the requesting user has administrative privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Vehica Core plugin to version 1.0.98 or later. Until the patch is applied, consider disabling the plugin or restricting user registration.

Recommended fix Moderate confidence

Vehica Core plugin version 1.0.98 or later

  1. Log in to the WordPress admin dashboard with administrator privileges
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Vehica Core plugin in the plugin list
  4. Click 'Update now' if an update is available, or manually update to version 1.0.98 or later
  5. Verify the plugin updated successfully by checking the version number
  6. Consider testing that users with Subscriber role cannot escalate to Administrator
  7. If available, review user accounts to ensure no unauthorized administrator accounts were created
Caveat No known breaking changes reported for this security update; standard minor/plugin update practices apply

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3105 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-3105 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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