# CVE-2026-8705: ClearSale Total <= 3.4.2 - Unauthenticated SQL Injection


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-58pf-7c32-vjf7

## What is CVE-2026-8705?

CVE-2026-8705 is a high-severity vulnerability in ClearSale Total, published on 24 Jun 2026. 

### Official description

The ClearSale Total plugin for WordPress is vulnerable to SQL Injection via the `pagseguro[metodo]` POST parameter of the `clearsale_total_push` AJAX action in all versions up to, and including, 3.4.2. The handler is registered for unauthenticated users (`wp_ajax_nopriv_clearsale_total_push`), and although a `wp_verify_nonce()` check exists, the failing branch's `die()` is commented out so execution continues regardless of nonce validity. On PHP < 8.0 the attacker-supplied `$metodo` value bypasses the `switch ($metodo) { case 4: ... }` guard via loose type juggling (the string `"4 AND SLEEP(5)"` compares equal to integer `4`), reaching an unquoted `UPDATE wp_cs_total_dadosextras SET metodo=$metodo, ...` query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation requires the target server to be running PHP < 8.0.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2026-8705 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8705 is a high-severity vulnerability in ClearSale Total, published on 24 Jun 2026. 
Exploitation: There is no known exploitation of CVE-2026-8705 in the wild and no public exploit code.

Affected product: ClearSale Total. 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-8705/ (Markdown: https://insights.sbomify.com/CVE-2026-8705/index.md)
```

## Sources

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

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