View Issue Details

Jump to NotesJump to History
This issue affects 1 person(s).
 0
IDProjectCategoryView StatusDate SubmittedLast Update
20526Bug reports_ Unknownpublic2026-05-21 07:322026-05-21 07:32
Reporterriadh2020 Assigned To 
PrioritynoneSeverityminor 
Status newResolutionopen 
Product Version6.14.x 
Summary20526: CSS Injection Bug in fruity_twentythree theme - Broken checkbox/radio checkmark unicode (content: "\";)
Description

When rendering a survey using the default fruity_twentythree core theme (or a child theme inheriting from it), an unescaped backslash bug occurs in the dynamically injected <style> block inside the <head>.

.checkbox-item input[type="checkbox"]:checked + label::after,
.checkbox-item input[type="radio"]:checked + label::after {
content: "\";
}
his unescaped single backslash treats the closing quote and semicolon as part of the string or breaks the CSS parser, preventing the checkmark icon from displaying correctly on checked boxes and radios. It seems like a core twig or database configuration variable for the icon unicode (e.g., \f00c) is being truncated or incorrectly escaped upon rendering.

Steps To Reproduce

Steps to reproduce

Create a survey using the standard fruity_twentythree theme.

View the source code of the active survey page.

Inspect the <style> block in the HTML <head>.

Notice the broken content: "\"; rule for .checkbox-item.

Expected result

The content property should either contain a valid font icon unicode string (like "\f00c") or be properly handled if empty, instead of exposing a raw broken backslash "\";.

Actual result

(Write here what happened instead)

TagsNo tags attached.
Bug heat0
Complete LimeSurvey version number (& build)LimeSurvey Community Edition Version 6.14.0+250520
I will donate to the project if issue is resolvedNo
BrowserFirfox
Database type & versionMySQL / MariaDB (via mysqlnd 8.1.33 / PDO)
Server OS (if known)Linux (Cluster d'hébergement OVH)
Webserver software & version (if known)
PHP Version8.1.33 (FPM/FastCGI)

Users monitoring this issue

There are no users monitoring this issue.

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2026-05-21 07:32 riadh2020 New Issue