# CVE-2026-49224: Vvveb post revision authorization bypass allows Authors to read, restore, or delete other Authors' post revisions

> Authors can read, restore, or delete other Authors' post revisions due to missing authorization checks in the Vvveb CMS backend.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-88w5-4x93-48rf

## What is CVE-2026-49224?

CVE-2026-49224 is a high-severity missing authorization vulnerability in givanz Vvveb, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vvveb is a powerful and easy to use CMS with page builder to build websites, blogs or ecommerce stores. Prior to 1.0.8.4, Vvveb backend post revision operations allow a low-privileged Author to access revisions for posts owned by another Author. The admin/controller/content/revisions.php controller and admin/sql/sqlite/post_content_revision.sql queries trust caller-controlled post_id, language_id, and created_at values without consistently applying the current admin_id to revision lists, reads, restores, and deletes. An attacker can read historic post content, restore a revision over another Author's live post content, or delete revision records, exposing drafts, corrupting published content, and removing audit history. This issue is fixed in version 1.0.8.4.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-49224 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49224 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-49224 is a high-severity missing authorization vulnerability in givanz Vvveb, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49224 exists.

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

## Sources

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

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