# CVE-2026-7859: Motors Car Dealership & Classified Listings < 1.4.110 - Unauthenticated Post-Meta Write via stm_ajax_add_a_car_media

> Unauthenticated attackers can modify arbitrary post metadata, including product prices, due to missing authorization checks in the Motors plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-6xrf-25hf-gfpv

## What is CVE-2026-7859?

CVE-2026-7859 is a medium-severity missing authorization vulnerability in Unknown Motors, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Motors  WordPress plugin before 1.4.110 does not have proper authorisation and CSRF checks on one of its AJAX actions, allowing unauthenticated attackers to modify arbitrary post metadata, such as the gallery, featured image and, on WooCommerce sites, product prices.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-7859 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7859 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7859 is a medium-severity missing authorization vulnerability in Unknown Motors, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7859 exists.

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-7859/ (Markdown: https://insights.sbomify.com/CVE-2026-7859/index.md)
```

## Sources

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

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