Motors Car Dealer\, Classifieds \& ListingWordPress extension · Stylemixthemes
CVE-2022-38716
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in StylemixThemes Motors – Car Dealer, Classifieds & Listing plugin <= 1.4.4 versions.
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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in StylemixThemes Motors WordPress plugin versions 1.4.4 and below allows attackers to induce authenticated users to perform unintended state-changing actions, such as modifying listings or plugin settings, by tricking them into submitting malicious requests.
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
Motors Car Dealer\, Classifieds \& ListingWordPress extension
<= 1.4.4CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed plugin versionLocate the Motors plugin in wp-content/plugins/ and read the main plugin file header, or use WP-CLI command: wp plugin list --name=motorsAffected if plugin version is 1.4.4 or lower
-
Verify WordPress admin access existsConfirm that administrator or editor accounts exist in the WordPress users table (wp_users) who can access the plugin settings or modify listingsAffected if any privileged user accounts exist in the WordPress installation
-
Inspect plugin for nonce implementationExamine the plugin PHP files for state-changing actions (POST/GET requests handling listings or settings) and check if wp_nonce_field or check_admin_referer is used on form submissionsAffected if forms handling listings or plugin settings lack nonce validation tokens
-
Review .htaccess or firewall logsCheck access logs for POST requests to admin-ajax.php or admin-post.php with the motors plugin action parameters that may indicate CSRF exploitation attemptsAffected if unusual or unauthorized POST requests to plugin endpoints are observed
You are affected if the Motors plugin version is 1.4.4 or below and your site has authenticated users with permissions to modify listings or plugin settings.
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 · scopedUpdate the plugin to version 1.4.5 or later which includes anti-CSRF nonce validation on all state-changing operations. Until patched, monitor for suspicious admin actions and educate users about not clicking untrusted links while logged in.
Version 1.4.5 or latest available version
- Backup your WordPress site and database before making any changes
- Navigate to the Plugins section in your WordPress admin dashboard
- Locate the 'Motors – Car Dealer, Classifieds & Listing' plugin
- Update the plugin to the latest available version (version 1.4.5 or higher)
- Clear any site caches and verify the update was successful
- Test critical site functionality to ensure the update did not break any features
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Motors Car Dealer\, Classifieds \& Listing
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38716 — 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-2022-38716 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