Skip to content
Noroxi
CVE-2026-44366· NVD / CVE Program· CNA GitHub_M

Vvveb: Stored XSS via Comment Author Field

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.

MediumCVSS 6.1 · v3.1—No exploit Fix available
Published
May 15, 2026
Updated
Jun 17, 2026
EPSS
0.3% · 18th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

24

Monitor

Low priority for now.

CVSS
24 / 40 · 6.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
6.1
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • givanz Vvveb

    • < 1.0.8.1affected

Same product

givanz: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-41930Vvveb < 1.0.8.2 Hard-coded Credentials Information Disclosure via phpMyAdmin
    36Monitor
  • CVE-2026-39918Vvveb < 1.0.8.1 Code Injection via Installation Endpoint
    36Monitor
  • CVE-2026-54612Vvveb: Authenticated editor path traversal to PHP file write/RCE via data-v-save-global
    35Monitor
  • CVE-2026-49228Vvveb product authorization bypass allows Vendors to read, duplicate, or delete other Vendors' products
    35Monitor
  • CVE-2026-49221Vvveb digital asset authorization bypass allows Vendors to list, read, edit, or delete other Vendors' digital assets
    35Monitor
  • CVE-2026-45800Vvveb: Authenticated SQL injection in /user/orders via order_by and direction
    34Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
givanz Vvveb1.0.8.1 · descriptionVendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-54506125 days apartVvveb: Stored XSS via sanitizeHTML() bypass in user profile bio field
    30Monitor
  • CVE-2026-456220 days apartVvveb: Unauthenticated reflected XSS in public product return form via customer_order_id
    21Monitor
  • CVE-2026-419321 days apartVvveb < 1.0.8.3 Stored XSS via Signup Controller
    21Monitor
  • CVE-2026-456160 days apartVvveb: Stored XSS in Posts allows privilege escalation via post editor
    20Monitor
  • CVE-2026-419298 days apartVvveb < 1.0.8.2 Unauthenticated Reflected XSS via Visual Editor
    20Monitor
  • CVE-2026-3442925 days apartVvveb < 1.0.8.1 Stored XSS via Media Upload and Rename
    20Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

nvd-secondary

Root cause

User content is inserted into the page as HTML. The browser interprets the content as code rather than data.

The bug in code

The whole CWE-79 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
commentEl.innerHTML = comment.body;

Fixed

ts
commentEl.textContent = comment.body;

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records