What is CVE-2026-66693?

CVE-2026-66693 is WordPress Motors plugin <= 1.4.113 - Broken Access Control vulnerability. The supplied enrichment data classifies it as Remote Code Exec mapped to CWE-862 CWE-862.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-66693. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-66693 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

A public PoC is not confirmed from current sources for CVE-2026-66693. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-66693 using CVSS 6.5, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

Workarounds are not confirmed from current sources. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

mediumRemote Code Exec

CVE-2026-66693

CVE-2026-66693 — WordPress Motors plugin <= 1.4.113 - Broken Access Control vulnerability

Q: Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Q: Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-66693. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Q: Is it in CISA KEV?

No. CVE-2026-66693 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Q: Is there a public exploit?

A public PoC is not confirmed from current sources for CVE-2026-66693. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

Q: How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

Q: How should teams prioritize it?

Prioritize CVE-2026-66693 using CVSS 6.5, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Q: Are workarounds available?

Workarounds are not confirmed from current sources. Fixed-version evidence is listed in the mitigation section above.

Q: Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

Q: What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

Subscriber Broken Access Control in Motors <= 1.4.113 versions.

Published Aug 13, 2026Updated Aug 13, 2026Sources: NVD, Stylemix (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

ahead of 0% of scored CVEs

Affects

Stylemix

Motors

CVSS base

6.5

medium

Remediation

The vendor's own words where we have them.

Update the WordPress Motors Plugin to the latest available version (at least 1.4.114).

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Stylemix	Motors	n/a to <= 1.4.113	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

None

Confidentiality

None

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
6.5	CVSS 3.1	medium	2.8	3.6	patchstack.com (CNA), Stylemix (CNA), GHSA

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-862 · Missing Authorization

Read Application Data
Read Files or Directories
Modify Application Data
Modify Files or Directories

Mitigation: Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.

Weakness & attack patterns

CWE-862

Inferred from the weakness class — not observed against this CVE.

CAPEC-242 · Code InjectionCAPEC-35 · Leverage Executable Code in Non-Executable Files

T1211Exploitation for Defensive Evasion
T1542.002Pre-OS Boot: Component Firmware
T1556Modify Authentication Process

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable Motors.

web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 6.5 (AV:N)
Aug 13, 2026 · NVD
Initial · CVE published
Aug 13, 2026 · NVD
Added · GHSA-r3c2-5pcc-7qp9 published (medium)
Aug 13, 2026 · GitHub Security Advisory

References

3 on the record

patchstack.com/database/wordpress/plugin/motors-car-dealership-classified-listings/vulnerability/wordpress-motors-plugin-1-4-113-broken-access-control-vulnerability?_s_id=cve
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2026-66693
NVD
github.com/advisories/GHSA-r3c2-5pcc-7qp9
Exploit, Third Party Advisory

Elsewhere on this site

Stylemixevery CVE for this vendor
Remote Code Execsame class
CWE-862other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-66693 is WordPress Motors plugin <= 1.4.113 - Broken Access Control vulnerability, a medium vulnerability affecting Motors from Stylemix. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-66693. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-66693. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 6.5 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.