CVE-2026-45622
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVvveb is a powerful and easy to use CMS with page builder to build websites, blogs or ecommerce stores. Prior to 1.0.8.3, there is an unauthenticated reflected cross-site scripting (XSS) issue in the public product return form in Vvveb CMS. The customer_order_id POST parameter is inserted into the Order %s not found! error message when the order lookup fails, and that message is rendered in the frontend template without HTML escaping. As a result, attacker-controlled HTML/JavaScript executes in the submitting user's browser. This vulnerability is fixed in 1.0.8.3.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceVvveb CMS prior to 1.0.8.3 contains an unauthenticated reflected XSS vulnerability in the public product return form. The customer_order_id POST parameter is directly inserted into an error message template ('Order %s not found!') without HTML encoding, allowing attackers to inject malicious HTML/JavaScript that executes in the victim's browser when the order lookup fails.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- P
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Vvveb CMS is installedLook for Vvveb-specific files such as /vendor/vvveb/ or check the footer of the website for 'Vvveb' branding, or access the /admin/ login page which displays the Vvveb logo.Affected if The target website is running Vvveb CMS.
-
Determine the installed Vvveb versionCheck the version file typically located at /vendor/vvveb/vvveb/VERSION.txt or look for a version number in the admin dashboard footer or in the source code meta tags.Affected if The installed version is earlier than 1.0.8.3.
-
Verify the product return form is publicly accessibleAccess the return form endpoint. The path may vary but commonly includes 'return' or 'order-return' in the URL. Check if the form accepts POST input without authentication.Affected if The return form exists and accepts unauthenticated requests.
-
Check if customer_order_id parameter reflects in error messagesSend a POST request to the return form with a crafted customer_order_id value (for example: <script>alert(1)</script>) and observe whether the value appears unescaped in the error response.Affected if The error message 'Order %s not found!' displays the injected payload without HTML encoding.
A target is affected if it runs Vvveb CMS version earlier than 1.0.8.3 and the public return form reflects the customer_order_id parameter unescaped in error messages.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to Vvveb CMS version 1.0.8.3 or later, which implements proper HTML escaping of user-supplied input in error messages. If immediate upgrade is not feasible, implement input validation and output encoding on the customer_order_id parameter at the application or WAF level.
1.0.8.3
- Backup the current Vvveb CMS installation and database
- Download Vvveb CMS version 1.0.8.3 or later from the official source (github.com/vvveb/vvveb)
- Upgrade the Vvveb CMS installation to version 1.0.8.3 following the standard upgrade procedure
- Verify the upgrade was successful and test the product return form to confirm the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45622 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45622 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data