CVE-2024-10970
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 · uneditedThe The Motors – Car Dealer, Classifieds & Listing plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 1.4.43. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute arbitrary shortcodes.
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 confidenceThe Motors WordPress plugin fails to validate user input before passing it to do_shortcode(), allowing authenticated users with Subscriber-level access or higher to inject and execute arbitrary shortcodes. This shortcode injection vulnerability enables attackers to potentially execute malicious code or access sensitive functionality depending on what shortcodes are registered on the site.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.4.44CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Motors plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Motors - Car Dealer, Classifieds & Listing' by Stylemixthemes. Note if it is active or inactive.Affected if The plugin is installed and active
-
Check installed version against affected rangeIn the plugins list, locate the Motors plugin version number. Compare it to the affected version range: versions below 1.4.44 are vulnerable.Affected if The installed version is lower than 1.4.44
-
Verify low-privilege user roles existGo to Users > Users List in WordPress admin. Check if any users have the 'Subscriber' role, or if new user registration is enabled allowing Subscriber-level access.Affected if Subscriber role users exist or user registration is enabled with default Subscriber role
-
Identify shortcode entry points accessible to usersSearch plugin code for do_shortcode() calls that process user-supplied input from frontend forms, profile fields, or submission pages. Common areas include vehicle listing submission forms, user profile fields, or search parameters.Affected if The plugin accepts and processes user input through do_shortcode() without sanitization
-
Review registered shortcodes on the siteSearch theme or plugin files for add_shortcode() calls to identify what functionality could be exploited if shortcode injection occurs. Look for shortcodes that expose sensitive data or actions.Affected if Shortcodes are registered that could allow privilege escalation or data exposure when injected
A site is affected if the Motors plugin version is below 1.4.44 and low-privilege users (Subscriber role) can access functionality that passes unsanitized input to do_shortcode().
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.4.44
Update the plugin to version 1.4.44 or later. If immediate update is not possible, restrict the 'subscriber' role permissions or disable shortcode functionality until the patch can be applied.
1.4.44
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Motors – Car Dealer, Classifieds & Listing' in the plugin list
- If an update is available, click 'Update Now' to upgrade to version 1.4.44
- Alternatively, go to Dashboard > Updates and select the plugin to update
- Alternatively, via WP-CLI run: wp plugin update motors
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10970 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-10970 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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