CVE-2026-116617 — WordPress
HIGHCVE-2026-116617 is a high-severity (CVSS 8.1) Path Traversal vulnerability. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
The Motors – Car Dealership & Classified Listings Plugin plugin for WordPress is vulnerable to File Deletion in all versions up to, and including, 1.4.128 The vulnerability exists because…
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Description
The Motors – Car Dealership & Classified Listings Plugin plugin for WordPress is vulnerable to File Deletion in all versions up to, and including, 1.4.128 The vulnerability exists because stm_save_user_extra_fields(), hooked to personal_options_update, writes the attacker-controlled stm_dealer_logo_path parameter directly to user meta without an ownership check binding the submitted path to the submitting user — unlike the stm_payment_status and stm_lost_password_hash fields, this field is not gated by a manage_options or edit_users capability check. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete image files belonging to other users under wp-content/uploads — including other users' avatars, dealer logos, and uploaded media — by storing a crafted path via their own profile and then triggering unlink() through the become-dealer form on their author page. Note that the two path guards (stm_mvl_is_path_within_uploads and stm_mvl_is_allowed_image_file) do restrict the attack surface to files with an image extension that resolve within the uploads basedir; files outside that directory, such as wp-config.php or plugin PHP files, cannot be reached.
Detection & mitigation playbook
VulnerabilityDetect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
The records we use list no fixed release for CVE-2026-116617. Check the upstream advisory for a patched version, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is CVE-2026-116617 in your dependencies?
Find it across your dependency tree, including transitive dependencies.