dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-27433

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 7 weeks old

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
Unauthenticated Broken Access Control in Motors <= 5.6.80 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 broken access control vulnerability in the Motors WordPress theme/plugin (versions <= 5.6.80) allows attackers to access sensitive functionality or data without any authentication credentials due to improper authorization checks.

MitigationUpgrade Motors to a version newer than 5.6.80 or apply the vendor's security patch to remediate the broken access control.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

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. Identify if Motors theme or plugin is installed
    Log into the WordPress admin dashboard and navigate to Appearance > Themes (for theme) or Plugins (for plugin) to confirm Motors is present
    Affected if Motors theme or plugin is not installed in WordPress
  2. Locate the installed version number
    In WordPress admin, go to Themes or Plugins page and find the Motors entry to view its version number, or check the main PHP file (typically functions.php or main plugin file) for the 'Version' header comment
    Affected if The displayed version number is 5.6.80 or lower
  3. Confirm the version is within affected range
    Compare your installed version against the vulnerable range: any version <= 5.6.80 is affected
    Affected if The installed version is 5.6.80 or any lower number
  4. Check for exposed admin or sensitive endpoints
    If accessible without authentication, attempt to access common WordPress admin paths (such as /wp-admin/admin-ajax.php with Motors-specific actions, or any custom Motors endpoints) to verify if authorization is enforced; review Motors plugin/theme files for function hooks that handle sensitive operations
    Affected if Sensitive functionality or data is accessible without requiring login credentials

You are affected if the Motors WordPress theme or plugin is installed and its version is 5.6.80 or lower, and unauthenticated access to sensitive functionality is possible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Motors to a version newer than 5.6.80 or apply the vendor's security patch to remediate the broken access control.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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 locally
dbcve dependency scanner

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