What it means
Your Content-Security-Policy allows scripts or objects from a wildcard: *, or a bare scheme such
as https:, http: or data: in script-src, object-src or default-src. That permits code from any
host.
Why it matters
An attacker who can inject a script tag can point it at any server they control, and the policy
lets it run. data: in script-src lets an injected tag carry its code inline. The policy looks strict but
doesn't block the attacks it is meant to stop. Wildcards often creep in when someone loosens a policy to
fix a broken widget and never narrows it again.
How to fix it
- List the hosts you actually load scripts from, such as
script-src 'self' https://cdn.example.net. - Prefer nonces with
'strict-dynamic', which avoid long host lists. - Set
object-src 'none'; plugins are almost never needed. - Remove
data:from script-src; images can keepdata:underimg-src.
Check it worked
Run the HTTP and security headers check again. The finding should be gone once no wildcard or bare scheme is allowed for scripts or objects.