# CVE-2023-6750: Clone < 2.4.3 - Unauthenticated Backup Download

- Exploited (CISA KEV): no
- Published: 2024-01-08
- CVSS: 7.5 HIGH (v3.1)
- EPSS: 2.0% (80th percentile)

The Clone WordPress plugin before 2.4.3 uses buffer files to store in-progress backup informations, which is stored at a publicly accessible, statically defined file path.

## Edge WAF coverage (claimed by vendors, not measured)

| Vendor | Status | First rule | Days after publication |
|---|---|---|---|
| Cloudflare | Before feed history | — | — |
| AWS | No public claim | — | — |
| Microsoft Azure | No public claim | — | — |
| Google Cloud | Before feed history | — | — |
| Fastly | Before feed history | — | — |
| F5 | Rule published | 2026-07-07 | 911 |
| Akamai | No public source | — | — |
| OWASP CRS | No public claim | — | — |

### F5

- 2026-07-07 · new · rule 200009363
  > Added: signature 200009363 "WordPress Clone Sensitive File Exposure" (Information Leakage, risk Medium), systems: WordPress. References: CVE-2023-6750.
  Source: https://docs.cloud.f5.com/docs-v2/platform/changelogs/security-details-changelog

## Our test (measured)

- OWASP Core Rule Set 4.25.0, paranoia level 1, anomaly threshold 5, default CRS settings: partial (1 of 2 requests blocked), template CVE-2023-6750, 2026-11-02
- OWASP Core Rule Set 4.25.0, paranoia level 2, anomaly threshold 5, default CRS settings: partial (1 of 2 requests blocked), template CVE-2023-6750, 2026-11-02

"No public claim" means no vendor statement names this CVE; "Before feed history" means the CVE is older than the vendor feed. In both cases generic rules may still block it.

HTML: https://cve.vigilbase.com/cve/CVE-2023-6750 · JSON: https://cve.vigilbase.com/api/v1/cves/CVE-2023-6750