dbcve.org
Motors Car Dealer\, Classifieds \& ListingWordPress extension · Stylemixthemes

CVE-2023-46208

MEDIUM · 6.1 CVSS v3.1 Published 2023-10-27
Fix available
A fix is available. Upgrade to after 1.4.6 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in StylemixThemes Motors – Car Dealer, Classifieds & Listing plugin <= 1.4.6 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 confidence

Unauthenticated reflected cross-site scripting (XSS) vulnerability in the StylemixThemes Motors WordPress plugin (Car Dealer, Classifieds & Listing) affecting versions 1.4.6 and below. Attackers can inject malicious JavaScript through unsanitized user input that gets reflected back in HTTP responses.

MitigationUpdate the StylemixThemes Motors plugin to a version newer than 1.4.6. If immediate updating is not feasible, deploy a WAF rule to filter XSS payloads and implement input validation/sanitization on any user-supplied parameters.

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
Affected:<= 1.4.6

CVSS 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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the StylemixThemes Motors plugin
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and find 'Motors - Car Dealer, Classifieds & Listing' by Stylemixthemes. Note the installed version displayed. Alternatively, check the plugin folder at /wp-content/plugins/motors/ and read the main plugin file (oftenmotors.php) to find the version constant.
    Affected if The displayed version is 1.4.6 or lower.
  2. Confirm the exact version number
    Read the plugin header in the main PHP file (typically /wp-content/plugins/motors/motors.php or /wp-content/plugins/motors/index.php) and locate the 'Version' field in the plugin comment header. Compare this number against the affected range.
    Affected if The version field shows 1.4.6 or any version number lower than 1.4.6.
  3. Identify accessible query parameters
    Audit the site for any publicly accessible URLs that accept user-supplied query parameters (GET requests). Common areas include search functions, filter parameters, sorting options, or any URL that echoes input back to the user. Use a browser or proxy to observe which parameters are reflected in the HTML response.
    Affected if Any parameter value supplied in the URL is returned unescaped or un-sanitized in the page source.
  4. Test for reflected content in HTTP responses
    Submit a benign test string such as <script>alert('test')</script> or similar XSS probe as a URL parameter value. Request the URL and inspect the raw HTTP response or page source to see if the payload is rendered as-is without encoding or escaping.
    Affected if The test string appears literally in the response HTML without being escaped to &lt;script&gt; or equivalent.

You are affected if the Motors plugin version is 1.4.6 or lower AND any user-supplied URL parameter is reflected in the response without proper HTML encoding.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to a release after 1.4.6
Interim mitigation

Update the StylemixThemes Motors plugin to a version newer than 1.4.6. If immediate updating is not feasible, deploy a WAF rule to filter XSS payloads and implement input validation/sanitization on any user-supplied parameters.

Fix this in Motors Car Dealer\, Classifieds \& Listing Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-46208 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-46208 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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