dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-54691

MEDIUM · 5.3 CVSS v3.1 Published 2025-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Authorization Bypass Through User-Controlled Key vulnerability in Stylemix Motors motors-car-dealership-classified-listings allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Motors: from n/a through <= 1.4.80.

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 · low confidence

Authorization bypass vulnerability in the Motors WordPress plugin (car dealership classified listings) where the application uses user-controlled input to determine access control levels, allowing unauthenticated or low-privilege attackers to bypass proper authorization checks and access resources or functionality they should not have access to.

MitigationUpdate the Motors plugin to a version beyond 1.4.80 which should contain proper access control validation, or audit and fix authorization logic to ensure access control decisions are not made based on user-controlled input.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

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

  1. Confirm Motors plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Motors' or 'Motors - Car Dealership & Classified Listings'. Alternatively, check the /wp-content/plugins/ directory for the stm-motors folder.
    Affected if The Motors plugin (stm-motors) is present in the WordPress installation
  2. Identify installed Motors version
    In WordPress admin > Plugins, find the Motors plugin and note the version number displayed. Or check the main plugin file header in /wp-content/plugins/stm-motors/stm-motors.php for the 'Version' comment.
    Affected if The version is 1.4.80 or lower (versions up to and including 1.4.80 are affected)
  3. Verify plugin is active
    In WordPress admin > Plugins, confirm the Motors plugin shows as 'Active'. Vulnerable code only executes when the plugin is active.
    Affected if The plugin is active with a vulnerable version (1.4.80 or below)
  4. Test for unauthorized access to sensitive endpoints
    If possible, attempt to access common Motors admin endpoints (such as /wp-admin/admin-ajax.php?action=stm_* or listing submission/comparison endpoints) without authentication or with a low-privilege subscriber account. Use a tool like Burp or curl to send requests without valid credentials.
    Affected if Requests return successful data or administrative functionality without proper authentication

The environment is affected if the Motors plugin is installed, active, and running version 1.4.80 or lower, where user-controlled input can influence authorization decisions.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Motors plugin to a version beyond 1.4.80 which should contain proper access control validation, or audit and fix authorization logic to ensure access control decisions are not made based on user-controlled input.

Recommended fix Moderate confidence

Version 1.4.81 or later (latest stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Motors – Car Dealership & Classified Listings' plugin
  4. Check if an update is available (if not, manually download the latest version from WordPress.org or Stylemix theme forest
  5. Update the plugin to the latest version available
  6. Verify the update was successful and test the classified listings functionality
  7. Ensure the updated version is 1.4.81 or higher
Caveat Review changelog for any breaking changes; test in staging if possible before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54691 — 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-2025-54691 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