# CVE-2026-106029: WeddingCity Lite <= 1.0.4 - Unauthenticated Arbitrary Post and Attachment Deletion

> Unauthenticated attackers can permanently delete arbitrary posts, pages, and media attachments due to missing authorization checks in the WeddingCity Lite plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 11 Oct 2026
- **Updated:** 11 Oct 2026
- **Also known as:** GHSA-m8g6-75j7-xq8j

## What is CVE-2026-106029?

CVE-2026-106029 is a high-severity missing authorization vulnerability in Unknown WeddingCity Lite, published on 11 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WeddingCity Lite  WordPress plugin through 1.0.4 does not perform any authorisation or validity checks before deleting posts, pages and media attachments, allowing unauthenticated attackers to permanently delete arbitrary content site-wide.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-106029 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-106029 is a high-severity missing authorization vulnerability in Unknown WeddingCity Lite, published on 11 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-106029 in the wild and no public exploit code.

Affected product: Unknown WeddingCity Lite. 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-106029/ (Markdown: https://insights.sbomify.com/CVE-2026-106029/index.md)
```

## Sources

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

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