# CVE-2026-82195: 10Web Booster < 2.34.0 - Unauthenticated Connection Secret Disclosure and Deletion

> Unauthenticated attackers can view and delete the cloud connection secret, causing denial of service for administrators.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-j28j-9pgq-m442

## What is CVE-2026-82195?

CVE-2026-82195 is a medium-severity vulnerability in Unknown 10Web Booster, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 10Web Booster  WordPress plugin before 2.34.0 does not restrict access to the routine which issues the shared secret that authenticates its cloud connection, disclosing that secret to unauthenticated visitors and letting them delete it repeatedly, preventing an administrator from completing a legitimate connection.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-82195 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82195 is a medium-severity vulnerability in Unknown 10Web Booster, published on 24 Sep 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-82195 in the wild and no public exploit code.

Affected product: Unknown 10Web Booster. 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-82195/ (Markdown: https://insights.sbomify.com/CVE-2026-82195/index.md)
```

## Sources

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

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