Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,075 of 9,075 pages
About the help in other languages
All help pages

Story: the Content Security Policy

A feature story about the Content Security Policy of Exponential - report-only on the administration by default, off on public sites, an administration rebuilt without inline scripts so a strict policy can be enforced…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/press/story-content-security-policy.md

On this page

Story: the Content Security Policy

This page is for technology and security journalists. A Content Security Policy is a browser rule that limits which scripts and styles a page may run. In October 2026 Exponential's administration was rebuilt so that a strict policy can be switched on. This page explains what that means and how to describe it accurately.

Contents

  1. The story in one paragraph
  2. What is new, and when
  3. Facts you can print
  4. What not to claim
  5. Explaining it to readers
  6. Angles and headline ideas
  7. Who to ask
  8. Related pages

The story in one paragraph

"A strict policy (script-src 'self', no 'unsafe-inline') means that a script injected into a page through a stored or reflected value does not run, even where a template forgets to escape it" (Content Security Policy). To make such a policy possible, the administration designs admin4 and admin4l were changed to carry "no inline <script>, no on...= attribute, no javascript: link, no style="" attribute and no <style> element" (6.0.15 changelog). The policy ships in report-only mode on the administration and off on public sites; the administrator decides when to enforce it, and rolling back is one setting.

What is new, and when

All in the 6.0.15 line, the current release line of Exponential 6.0; the dates are dates of the changes, not a release date.

WhatWhenSource
The policy setting, report-only on the administration by default16 October 20266.0.15 changelog
The administration without inline scripts, handlers and styles16 October 20266.0.15 changelog
What enforcing needs: extra sources, a nonce per request, a stricter companion policy17 October 20266.0.15 changelog
Reports in a log of their own, with rate limits17 October 20266.0.15 changelog
Extensions without inline scripts in their templates17 October 20266.0.15 changelog

Facts you can print

FactSource
By default the policy is "report-only on the administration and off on the sites".Content Security Policy
The shipped policy allows scripts and styles from the site itself only ('self') and blocks plugins (object-src 'none').Content Security Policy, Settings
In report-only mode the browser reports what it would block and blocks nothing.same
Rolling back from enforce is one setting: Mode=report-only.6.0.15 changelog
The online editor falls back from TinyMCE 3 to TinyMCE 8 where a strict policy is enforced.same
New administration templates may carry no inline styles or scripts; contributors must follow the rule.CONTRIBUTING.md
Reports go to var/log/csp.log, rate limited per client and in total.6.0.15 changelog

What not to claim

  • "Exponential blocks cross-site scripting." By default the administration only reports; enforcement is the administrator's decision, and public sites have no policy unless one is set.
  • "Every extension is ready for an enforced policy." The changelog keeps a shrinking allowlist of extensions that still have inline code.
  • "The CSP protects you" without the mode. Always say report-only or enforced.

Explaining it to readers

A Content Security Policy is a list the website sends to the browser: "only run scripts that come from my own
server". If an attacker manages to slip a script into a page, the browser refuses to run it. Exponential's
administration was rewritten so that this list can be strict. It starts in "report" mode, where the browser
only tells the site what it would have blocked.

Angles and headline ideas

"Rewriting an administration so the browser can say no"
"Report first, enforce later: how Exponential rolls out a strict browser policy"
"No inline scripts: the quiet security rule behind Exponential's new admin"

Who to ask

QuestionAskWhere
Why report-only first, plans for enforcing7x[email protected], or https://exponential.earth/about/contact-us
A bypass or vulnerabilityprivately[email protected] (SECURITY.md)

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x