YesWiki before 4.6.7 contains a stored cross-site scripting vulnerability in the Bazar FileField, which validates only the upload's file extension… (CVE-2026-104461)
YesWiki versions before 4.6.7 have a stored cross-site scripting (XSS) vulnerability in the Bazar FileField. This vulnerability arises because the system only validates the file extension of uploads and does not sanitize SVG files using HtmlPurifierService::cleanFile. As a result, malicious SVG files containing scripts can be stored and served inline, allowing authenticated users to execute scripts in the context of the wiki origin. This can lead to compromise of administrator sessions or accounts.
AI Analysis
Technical Summary
The vulnerability in YesWiki prior to version 4.6.7 is a stored cross-site scripting flaw located in the Bazar FileField component. The flaw exists because the upload validation process only checks the file extension and does not invoke HtmlPurifierService::cleanFile to sanitize SVG files. Consequently, SVG files containing embedded scripts are stored verbatim and served with the image/svg+xml MIME type. Authenticated users can exploit this by submitting crafted SVG files via POST requests to /api/entries/{formId}, causing script execution in the wiki's origin context and potentially compromising administrator sessions or accounts.
Potential Impact
An authenticated user can exploit this vulnerability to execute arbitrary scripts in the context of the wiki origin. This can lead to the compromise of administrator sessions or accounts, potentially allowing unauthorized actions within the application. The CVSS score is 5.4 (medium severity), reflecting limited but significant impact on confidentiality and integrity without direct availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict authenticated user permissions to limit file uploads or disable SVG file uploads if possible. Monitor vendor channels for updates regarding a patch or official fix.
YesWiki before 4.6.7 contains a stored cross-site scripting vulnerability in the Bazar FileField, which validates only the upload's file extension… (CVE-2026-104461)
Description
YesWiki versions before 4.6.7 have a stored cross-site scripting (XSS) vulnerability in the Bazar FileField. This vulnerability arises because the system only validates the file extension of uploads and does not sanitize SVG files using HtmlPurifierService::cleanFile. As a result, malicious SVG files containing scripts can be stored and served inline, allowing authenticated users to execute scripts in the context of the wiki origin. This can lead to compromise of administrator sessions or accounts.
CVSS v3.1
Score 5.4medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in YesWiki prior to version 4.6.7 is a stored cross-site scripting flaw located in the Bazar FileField component. The flaw exists because the upload validation process only checks the file extension and does not invoke HtmlPurifierService::cleanFile to sanitize SVG files. Consequently, SVG files containing embedded scripts are stored verbatim and served with the image/svg+xml MIME type. Authenticated users can exploit this by submitting crafted SVG files via POST requests to /api/entries/{formId}, causing script execution in the wiki's origin context and potentially compromising administrator sessions or accounts.
Potential Impact
An authenticated user can exploit this vulnerability to execute arbitrary scripts in the context of the wiki origin. This can lead to the compromise of administrator sessions or accounts, potentially allowing unauthorized actions within the application. The CVSS score is 5.4 (medium severity), reflecting limited but significant impact on confidentiality and integrity without direct availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict authenticated user permissions to limit file uploads or disable SVG file uploads if possible. Monitor vendor channels for updates regarding a patch or official fix.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-c49r-h57h-8wfx
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-104461"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6abfee8ea43b0b3b89e5503a
Added to database: 10/02/2026, 17:49:02 UTC
Last enriched: 10/02/2026, 17:58:58 UTC
Last updated: 10/02/2026, 21:26:05 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.