HIGHCVE-2026-3892CVSS 8.1

CVE-2026-3892: Arbitrary File Access in Motors Plugin

Platform

wordpress

Component

motors-car-dealership-classified-listings

Fixed in

1.4.108

CVE-2026-3892 is an arbitrary file access vulnerability discovered in the Motors – Car Dealership & Classified Listings Plugin for WordPress. This flaw allows authenticated users, even those with subscriber-level access, to delete files on the server. The vulnerability impacts versions 1.0.0 through 1.4.107, and a patch is available in version 1.4.108.

WordPress

Detect this CVE in your project

Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.

Impact and Attack Scenarios

An attacker exploiting this vulnerability can delete critical system files, potentially leading to a complete compromise of the WordPress installation. This could include deleting configuration files, database connections, or even core WordPress files. The ability to delete arbitrary files grants significant control over the server, enabling attackers to disrupt operations, steal sensitive data, or install malicious code. While requiring authentication, the low privilege level needed (subscriber) expands the potential attack surface significantly, as many WordPress sites have numerous users with this access level.

Exploitation Context

This vulnerability was published on 2026-05-14. Currently, there are no known public exploits or active campaigns targeting this specific vulnerability. The ease of exploitation, combined with the widespread use of WordPress and the plugin, suggests it could become a target for opportunistic attackers. Monitor security advisories and threat intelligence feeds for any indications of exploitation.

Threat Intelligence

Exploit Status

Proof of ConceptUnknown
CISA KEVNO
Internet ExposureHigh
Reports2 threat reports

CISA SSVC

Exploitationnone
Automatableno
Technical Impactpartial

CVSS Vector

THREAT INTELLIGENCE· CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H8.1HIGHAttack VectorNetworkHow the attacker reaches the targetAttack ComplexityLowConditions required to exploitPrivileges RequiredLowAuthentication level needed to attackUser InteractionNoneWhether a victim must take actionScopeUnchangedImpact beyond the vulnerable componentConfidentialityNoneRisk of sensitive data exposureIntegrityHighRisk of unauthorized data modificationAvailabilityHighRisk of service disruptionnextguardhq.com · CVSS v3.1 Base Score
What do these metrics mean?
Attack Vector
Network — remotely exploitable over the internet. No physical or local access required. Widest attack surface.
Attack Complexity
Low — no special conditions required. Attacker can exploit reliably without depending on rare configurations or timing.
Privileges Required
Low — any valid user account is sufficient. Basic authenticated access required.
User Interaction
None — attack is automatic and silent. Victim does nothing: no click, no file open.
Scope
Unchanged — impact is limited to the vulnerable component itself.
Confidentiality
None — no confidentiality impact. Attacker cannot read protected data.
Integrity
High — attacker can write, modify, or delete any data: databases, config files, or code.
Availability
High — complete crash or resource exhaustion. Full denial of service.

Affected Software

Componentmotors-car-dealership-classified-listings
Vendorwordfence
Minimum version1.0.0
Maximum version1.4.107
Fixed in1.4.108

Weakness Classification (CWE)

Timeline

  1. Reserved
  2. Published

Mitigation and Workarounds

The primary mitigation is to immediately upgrade the Motors plugin to version 1.4.108 or later. If upgrading is not immediately feasible due to compatibility issues or breaking changes, consider restricting file upload permissions for users with subscriber roles. Implement a Web Application Firewall (WAF) rule to block requests containing suspicious file paths in the logo upload parameter. Regularly review user permissions and ensure the principle of least privilege is enforced. After upgrading, confirm the fix by attempting to upload a file with a deliberately invalid path and verifying that the upload fails with an appropriate error message.

How to fix

Update to version 1.4.108, or a newer patched version

Frequently asked questions

What is CVE-2026-3892 — Arbitrary File Access in Motors Plugin?

CVE-2026-3892 is a HIGH severity vulnerability in the Motors plugin for WordPress, allowing authenticated users to delete arbitrary files on the server due to insufficient file path validation during logo uploads.

Am I affected by CVE-2026-3892 in Motors Plugin?

You are affected if your WordPress site uses the Motors plugin and is running version 1.0.0 through 1.4.107. Check your plugin version immediately.

How do I fix CVE-2026-3892 in Motors Plugin?

Upgrade the Motors plugin to version 1.4.108 or later to resolve the vulnerability. If immediate upgrade is not possible, restrict file upload permissions for subscriber roles and implement WAF rules.

Is CVE-2026-3892 being actively exploited?

As of the publication date, there are no known public exploits or active campaigns targeting CVE-2026-3892, but the vulnerability's ease of exploitation makes it a potential target.

Where can I find the official Motors plugin advisory for CVE-2026-3892?

Refer to the official Motors plugin website or WordPress plugin repository for the latest advisory and update information regarding CVE-2026-3892.

Is your project affected?

Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.

WordPress

Detect this CVE in your project

Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.

livefree scan

Scan your WordPress project now — no account

Upload any manifest (composer.lock, package-lock.json, WordPress plugin list…) or paste your component list. You get a vulnerability report instantly. Uploading a file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.

Manual scanSlack/email alertsContinuous monitoringWhite-label reports

Drag & drop your dependency file

composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...