Motors Car Dealer\, Classifieds \& ListingWordPress extension · Stylemixthemes
CVE-2023-46207
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 · uneditedServer-Side Request Forgery (SSRF) vulnerability in StylemixThemes Motors – Car Dealer, Classifieds & Listing.This issue affects Motors – Car Dealer, Classifieds & Listing: from n/a through 1.4.6.
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 confidenceServer-Side Request Forgery (SSRF) vulnerability in the Motors WordPress theme allows unauthenticated attackers to make the server perform arbitrary requests to internal or external resources. The vulnerability exists in versions through 1.4.6, likely in a feature that accepts URL input without proper validation.
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.6CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 theme is installedIn WordPress admin, go to Appearance > Themes and verify the Motors theme by Stylemixthemes is active. Note the installed version number displayed on the theme card.Affected if The Motors theme version displayed is 1.4.6 or lower (e.g., 1.4.6, 1.4.5, 1.4.0, etc.)
-
Check theme version numberLocate the version string in the theme's style.css file (typically at /wp-content/themes/motors/style.css) or in the theme's main PHP file. Look for 'Version:' declaration.Affected if The version number is 1.4.6 or any lower version number
-
Identify URL input featuresSearch the theme files for functions that accept URLs as input. Common locations include theme option panels, import/export functionality, or any feature described as fetching external data. Look for parameters named 'url', 'link', 'href', or similar in form submissions.Affected if Any feature in the theme settings accepts user-supplied URL input without visible validation checks
-
Verify feature accessibilityCheck if the identified URL-accepting feature is accessible to unauthenticated users. Test whether the feature can be triggered without logging into WordPress admin, or inspect the code for capability checks.Affected if The feature accepting URL input is accessible without authentication or with low-privileged user access
Your environment is affected if the Motors theme version is 1.4.6 or lower AND a URL-input feature exists and is accessible without proper validation.
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.
From vendor dataApply the vendor patch/更新 when available. Until then, restrict outgoing network access from the web server and monitor for suspicious outbound requests.
Fix this in Motors Car Dealer\, Classifieds \& Listing
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46207 — 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-2023-46207 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