.
EDIT: ggppdk, you posted before me while I was writing
This may or may not have anything to do with FLEXIcontent.
In your first post the error message appears to tell us this is an issue with a cookie,
and that the cookie contains
0=0 ( [data "0=0"] ).
Apparently the mod_sec rule does not like that pattern of data.
A search on the internet for that error code reveals the same or similar error messages with many types of websites - including Joomla, WordPress, ecommerce, others CMSs, etc.
So this could also be an issue with a browser hijack, a bad browser plug-in, an infection on your system, etc., etc.
There were some other examples found in my search where a cookie with
"1=1" triggered the rule.
The cookie could come from a number of different sources.
Joomla, Joomla extension, JavaScript, browser plug-in, etc. ...
Need to look at the contents the cookies for that website on your system.
Then it may be possible to tell if this has anything to do with FLEXIcontent.
.