Vvveb: Stored XSS via sanitizeHTML() bypass in user profile bio 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.5, app/controller/user/profile.php accepts the user[bio] field and passes stored content through sanitizeHTML() in system/functions.php, whose on* event-handler regular expression omits the forward-slash delimiter and whose do-while condition compares the string to itself, so forbidden nested tags are removed only once. An Author-role or higher user can submit solidus-prefixed event-handler markup or nested forbidden tags that survive sanitization. The stored bio is rendered without sufficient output encoding on /author/{username}, in the admin user-management view, and potentially in comment displays, causing attacker-controlled JavaScript to execute when unauthenticated visitors, administrators, or other users view the content. This can expose browser-session data and permit victim-context account actions, defacement, or phishing. This issue is fixed in version 1.0.8.5.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-54506
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 18:16 UTC · Revision 1
Source evidence
Vvveb: Stored XSS via sanitizeHTML() bypass in user profile bio field
core-osv · Original sourcePublished 17 Sept 2026, 21:47 UTC
Vvveb is a powerful and easy to use CMS with page builder to build websites, blogs or ecommerce stores. Prior to 1.0.8.5, app/controller/user/profile.php accepts the user[bio] field and passes stored content through sanitizeHTML() in system/functions.php, whose on* event-handler regular expression omits the forward-slash delimiter and whose do-while condition compares the string to itself, so forbidden nested tags are removed only once. An Author-role or higher user can submit solidus-prefixed event-handler markup or nested forbidden tags that survive sanitization. The stored bio is rendered without sufficient output encoding on /author/{username}, in the admin user-management view, and potentially in comment displays, causing attacker-controlled JavaScript to execute when unauthenticated visitors, administrators, or other users view the content. This can expose browser-session data and permit victim-context account actions, defacement, or phishing. This issue is fixed in version 1.0.8.5.
osv:CVE-2026-54506
Complete source record
{
"id": "a2824ed1d13b4d012e783ded09c2436daeb4c7ad8c8bc05df6b04737a213d420",
"url": "https://osv.dev/vulnerability/CVE-2026-54506",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Vvveb: Stored XSS via sanitizeHTML() bypass in user profile bio field",
"summary": "Vvveb is a powerful and easy to use CMS with page builder to build websites, blogs or ecommerce stores. Prior to 1.0.8.5, app/controller/user/profile.php accepts the user[bio] field and passes stored content through sanitizeHTML() in system/functions.php, whose on* event-handler regular expression omits the forward-slash delimiter and whose do-while condition compares the string to itself, so forbidden nested tags are removed only once. An Author-role or higher user can submit solidus-prefixed event-handler markup or nested forbidden tags that survive sanitization. The stored bio is rendered without sufficient output encoding on /author/{username}, in the admin user-management view, and potentially in comment displays, causing attacker-controlled JavaScript to execute when unauthenticated visitors, administrators, or other users view the content. This can expose browser-session data and permit victim-context account actions, defacement, or phishing. This issue is fixed in version 1.0.8.5.",
"evidence": "osv:CVE-2026-54506",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-54506",
"aliases": [
"CVE-2026-54506",
"GHSA-5cg7-phhv-4qjr"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/givanz/vvveb",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "c8fef41ad8651d348050c513451755ab8882b97e"
},
{
"fixed": "20a01ef08559ffdc97205edeecde86c8ea27e567"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "1.0.8.5"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "20a01ef08559ffdc97205edeecde86c8ea27e567"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "c8fef41ad8651d348050c513451755ab8882b97e"
}
],
"source": "REFERENCES_TAG",
"original_tag": "1.0.8.5"
}
]
}
}
],
"versions": [
"1.0.8.4",
"1.0.8.3",
"1.0.8.2",
"1.0.8.1",
"1.0.8",
"1.0.7.3",
"1.0.7.2",
"1.0.7.1",
"1.0.7",
"1.0.6",
"1.0.5",
"1.0.4",
"1.0.3",
"1.0.2",
"1.0.1",
"1.0.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-54506.json"
}
}
],
"modified": "2026-10-28T02:30:22.036700686Z",
"provider": "osv",
"references": [
"https://github.com/givanz/Vvveb/releases/tag/1.0.8.5",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/54xxx/CVE-2026-54506.json",
"https://github.com/givanz/Vvveb/security/advisories/GHSA-5cg7-phhv-4qjr",
"https://nvd.nist.gov/vuln/detail/CVE-2026-54506",
"https://github.com/givanz/Vvveb/commit/20a01ef08559ffdc97205edeecde86c8ea27e567"
],
"provider_metadata": {
"cwe_ids": [
"CWE-116",
"CWE-185",
"CWE-79"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/54xxx/CVE-2026-54506.json"
}
},
"related_cves": [
{
"value": "CVE-2026-54506",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 488217,
"published_at": "2026-09-17T21:47:20.53+00:00"
}