# CVE-2024-1718: Business logic in Claudio Sanches – Checkout Cielo for WooCommerce

> Unauthenticated attackers can bypass payment validation to mark orders as paid, leading to unauthorized data modification and financial loss.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 4 Jun 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-f96c-86vh-rwfq

## What is CVE-2024-1718?

CVE-2024-1718 is a medium-severity vulnerability in claudiosanches Claudio Sanches – Checkout Cielo for WooCommerce, published on 4 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Claudio Sanches – Checkout Cielo for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data due to insufficient payment validation in the update_order_status() function in all versions up to, and including, 1.1.0. This makes it possible for unauthenticated attackers to update the status of orders to paid bypassing payment.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2024-1718?


## How do I fix CVE-2024-1718?

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

## Is CVE-2024-1718 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1718 and fix it if it is affected.

What it is: CVE-2024-1718 is a medium-severity vulnerability in claudiosanches Claudio Sanches – Checkout Cielo for WooCommerce, published on 4 Jun 2024. 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-2024-1718 in the wild and no public exploit code.

Affected product: claudiosanches Claudio Sanches – Checkout Cielo for WooCommerce. 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-2024-1718/ (Markdown: https://insights.sbomify.com/CVE-2024-1718/index.md)
```

## Sources

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

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