CVE-2026-104746 · Package
NO FIX YET · SEE WHAT TO DO
The Motors car dealership and classified listings plugin for WordPress fails to validate file paths in its user data save handler. Any logged-in subscriber can delete files under wp-content/uploads, and deleting the right file can lead to remote code execution.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the Motors car dealership and classified listings WordPress plugin at version 1.4.125 or earlier that allow subscriber-level accounts. Sites without this plugin, or where no one can log in, are not exposed. The sources do not say whether non-default configurations change exposure.
Not affected if no-subscriber-accounts, plugin-not-installed
Who cares motors-plugin, self-hosted, wordpress, wordpress-plugin
wp-content/plugins/ header of the main plugin file.1.4.125 are affected; the sources do not state a fixed version.The Motors – Car Dealership & Classified Listings Plugin plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the stm_listings_ajax_save_user_data function in all versions up to, and including, 1.4.125 This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). Although deletion is bounded to wp-content/uploads (preventing removal of wp-config.php), any authenticated Subscriber can trivially exploit this because the required AJAX nonce is printed on every front-end page and the handler's stm_user_avatar_path meta is writable by any logged-in user against their own account.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.