# CVE-2025-2568: Missing authorization in Vayu Blocks – Gutenberg Blocks for WordPress & WooCommerce

> Unauthenticated attackers can read and modify specific plugin options due to missing capability checks in Vayu Blocks for WordPress.

- **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:** 8 Apr 2025
- **Updated:** 8 Apr 2025
- **Also known as:** GHSA-89wq-8x6h-qwcm

## What is CVE-2025-2568?

CVE-2025-2568 is a medium-severity missing authorization vulnerability in themehunk Vayu Blocks – Gutenberg Blocks for WordPress & WooCommerce, published on 8 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Vayu Blocks – Gutenberg Blocks for WordPress & WooCommerce plugin for WordPress is vulnerable to unauthorized access and modification of data due to missing capability checks on the 'vayu_blocks_get_toggle_switch_values_callback' and 'vayu_blocks_save_toggle_switch_callback' function in versions 1.0.4 to 1.2.1. This makes it possible for unauthenticated attackers to read plugin options and update any option with a key name ending in '_value'.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-2568?


## How do I fix CVE-2025-2568?

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

## Is CVE-2025-2568 being exploited?

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

Public exploit code:

- Proof of Concept for CVE-2025-2568 (github_poc): https://github.com/shinigami-777/PoC_CVE-2025-2568

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2568 and fix it if it is affected.

What it is: CVE-2025-2568 is a medium-severity missing authorization vulnerability in themehunk Vayu Blocks – Gutenberg Blocks for WordPress & WooCommerce, published on 8 Apr 2025. 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-2025-2568 in the wild and no public exploit code.

Affected product: themehunk Vayu Blocks – Gutenberg Blocks for WordPress & 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-2025-2568/ (Markdown: https://insights.sbomify.com/CVE-2025-2568/index.md)
```

## Sources

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

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