# CVE-2026-91023: Missing authorization in Motors

> Authenticated subscribers can modify metadata on posts they do not own, including product prices, when specific non-default configurations are enabled.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-whfp-wchg-v9xw

## What is CVE-2026-91023?

CVE-2026-91023 is a low-severity missing authorization vulnerability in Unknown Motors, published on 2 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Motors  WordPress plugin before 1.4.124 does not properly verify that a user is authorised to modify a listing before processing one of its listing management actions, allowing authenticated attackers with subscriber-level access and above to set metadata on posts they do not own, including overwriting product prices. Exploitation is possible only when WooCommerce is active and the Motors  WordPress plugin before 1.4.124's paid featured-listing option is enabled, neither of which is a default configuration.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-91023?


## How do I fix CVE-2026-91023?

No fix has been published for CVE-2026-91023 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-91023 being exploited?

There is no known exploitation of CVE-2026-91023 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-91023 and fix it if it is affected.

What it is: CVE-2026-91023 is a low-severity missing authorization vulnerability in Unknown Motors, published on 2 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-91023 in the wild and no public exploit code.

Affected product: Unknown Motors. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-91023/ (Markdown: https://insights.sbomify.com/CVE-2026-91023/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-91023
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-91023
- OSV: https://osv.dev/vulnerability/CVE-2026-91023

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-91023/
Summaries are generated and may contain mistakes; the official description above is the record.