CSP are a work in progress, and should be part of the forthcoming OpenACS 5.8.1 release. Due to recent cahnges OpenACS has a CSP generator, which can produce for every page a potentially different CSP based on the requirements of the page. If one is using e.g. richtext editors, one to allow the directive 'unsafe-eval' for script-src, which one should not use in general. However, the usage of a richtext editor on some pages should not force the usage of this permissive CSP for the whole site, therefore one needs tailored CSPs. By using these automatically generated content security policy OpenACS.org recieves from securityheaders.io an A+ rating [1].
In general, the usage of content security policy generator can be controlled via the kernel parameter CSPEnabledP, where it can be turned on or off.
In your particular case, it looks to me as if you have updated acs-core, but not the openacs-bootstrap3-theme package. Can this be the case?
all the best
-gn
[1] https://securityheaders.io/?q=openacs.org&hide=on&followRedirects=on