# CVE-2026-83492: WordPress Kubio AI Website Builder - Denial Of Service

> An attacker can cause a denial of service in the Kubio AI Website Builder WordPress plugin due to improper input validation.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-5mqc-wggr-wp64

## What is CVE-2026-83492?

CVE-2026-83492 is a medium-severity denial of service vulnerability in Extend Themes Kubio AI Website Builder, published on 31 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper input validation vulnerability in Extend Themes Kubio AI Website Builder.

This issue affects Kubio AI Website Builder: before 2.9.1.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-83492 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-83492 is a medium-severity denial of service vulnerability in Extend Themes Kubio AI Website Builder, published on 31 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-83492 in the wild and no public exploit code.

Affected product: Extend Themes Kubio AI Website Builder. 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-83492/ (Markdown: https://insights.sbomify.com/CVE-2026-83492/index.md)
```

## Sources

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

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